server side route statements are affected by 'topology subnet'
|Reported by:||janjust||Owned by:|
|Severity:||Not set (if unsure, select this one)||Keywords:||topology subnet|
The sample config
server 10.8.0.0 255.255.255.0
route 192.168.4.0 255.255.255.0
works without any issues. If I add
OpenVPN ROUTE: OpenVPN needs a gateway parameter for a
--route option and no default was specified by either
--route-gateway or --ifconfig options
OpenVPN ROUTE: failed to parse/resolve route for
The same happens if you switch from 'dev tun' to 'dev tap'.
This is (at the very least) confusing to server admins.
A work around is to use
route 192.168.4.0 255.255.255.0 10.8.0.1
in this case but it is a pity that the VPN server IP needs to be explicitly mentioned. Perhaps a special keyword would help, e.g.
route 192.168.4.0 255.255.255.0 vpn_server_ip
Similar things are true for 'iroute' statements