Code: Select all
server 192.168.3.0 255.255.255.0
route-delay 10 20
This is not stated in manual. So is this a bug?Options error: --route-delay cannot be used with --mode server
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Code: Select all
server 192.168.3.0 255.255.255.0
route-delay 10 20
This is not stated in manual. So is this a bug?Options error: --route-delay cannot be used with --mode server
so 'route-delay' only makes sense when a connection is established. as routes are not added to a server when a client connects this option does not make sense - I'm not sure if the manual page should explicitly mention that.--route-delay [n] [w]
Delay n seconds (default=0) after connection establishment, before adding routes. If n is 0, routes will be added immediately upon connection establishment. If --route-delay is omitted, routes will be added immediately after TUN/TAP device open and --up script execution, before any --user or --group privilege downgrade (or --chroot execution.)
This option is designed to be useful in scenarios where DHCP is used to set tap adapter addresses. The delay will give the DHCP handshake time to complete before routes are added.
in config file, we make OpenVPN to use it's internal DCHP. On linux the tun/tap device is also set to dhcp. Why not to wait the routes addition some time? Oh, the thing is that in Windows its working as expected without giving this error. Why windows and linux interpret this two options differently?server 192.168.3.0 255.255.255.0
After a while I get the idea on "mode server". But. "route-delay" makes sense when a connection is established, or (on server) when tun-adapter is brought up and got an ip.so 'route-delay' only makes sense when a connection is established