You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an OpenVPN instance is configured with Topology subnet and a Client Override is used with Push reset option, the topology does not get pushed to the client (as per OpenVPN documentation) some clients (like on Mac OS) will complain that the pushed IP is wrong (as default is net30)
To Reproduce
Steps to reproduce the behavior:
Configure a OpenVPN Instance with topology subnet
Configure a client specific override with advances push reset option (so not to push all the options specifically the subnets) and set the specific pushed IP
Connect using OpenVPN which should complain about the wrong ifconfig push option
Expected behavior
There should also be an option in the Client Specific Override to set topology subnet (or a general additional settings option to put specific other settings)
Describe alternatives you considered
If you use "topology subnet" in the client export on Windows it seems to be working
The text was updated successfully, but these errors were encountered:
I'm not sure, it probably depends on the client, but I would expect these options in the client config to be honest. you can always experiment yourself, the client specific overwrites are flushed to disk in this function :
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
If an OpenVPN instance is configured with Topology subnet and a Client Override is used with Push reset option, the topology does not get pushed to the client (as per OpenVPN documentation) some clients (like on Mac OS) will complain that the pushed IP is wrong (as default is net30)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should also be an option in the Client Specific Override to set topology subnet (or a general additional settings option to put specific other settings)
Describe alternatives you considered
If you use "topology subnet" in the client export on Windows it seems to be working
The text was updated successfully, but these errors were encountered: