Lawrence Hi, Would it be possible to add an option to ignore push routes that conflict with the local IP address. Fri Mar 09 09:52:07 2012 WARNING: potential route subnet conflict between local LAN [172.16.1.0/255.255.255.0] and remote VPN [172.16.1.0/255.255.255.0] Fri Mar 09 09:52:07 2012 C:\WINDOWS\system32\route.exe ADD 172.16.1.0 MASK 255.255.255.0 198.18.0.6 OpenVPN recognises the potential conflict, an option not to add the route would be very helpfull. I have clients who connect remotely and need access to the office LAN and remote machines, but also need to connect from the office LAN to access the remoate machines. Cheers Lawrence
janjust you can tell the openvpn client to ignore ALL pushed routes using route-nopull It's not possible to ignore specific routes (this would pose many new problems, actually, as routes can depend on another)
Lawrence Hi janjust, I have tried the -nopull option and it works as it is intended but I would have to add each route that I did want manually to the config. Every time a new machine was commisioned I would need to edit the configs of all our users. My current work around is to have 2 configs for each user. 1 for remote access and 1 local. The local config adds the lines "--script-security 2" and "--route-up cmd.bat" where cmd.bat contains the line "C:\WINDOWS\system32\route.exe DELETE 172.16.1.0 MASK 255.255.255.0 198.18.0.6" which I copied directly form the section of the log file where the routes are deleted after a disconnect. This deletes the route as soon as it's been added. It's not perfect because it deletes both the route added for the VPN and the original route for the LAN connection but the local LAN is still accessible so I'm running with it.
janjust another trick would be to use a 'route-up' script in combination with 'route-noexec' : this script can then check for the route that you do NOT want added . It will still be a kludge, however.
