Actions
Bug #11448
closedIncorrect order of ``route-nopull`` option in OpenVPN client-specific override configuration
Start date:
02/18/2021
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:
Description
https://openvpn.net/faq/overriding-a-pushed-route-in-the-clients-config-throws-an-error/:
When connecting to server that pushes routes using this:
... # Pushed routes push "route 10.1.0.0 255.255.255.0"
and when the client overrides them in its config:
... # Options client route-nopull route 10.1.0.0 255.255.255.128 route-metric 50
...
This works but the client’s log have this:
Options error: option 'route' cannot be used in this context
This issue materializes because “route-nopull” option takes away the permission from the client to install server-pushed routes, effectively telling the option parser “no, this option is not valid here”.
The way to configure it correctly is then:
... # Options client route 10.1.0.0 255.255.255.128 route-metric 50 route-nopull
The "route-nopull" option must be placed after the entered "Custom options" to avoid this error
Actions