id summary reporter owner description type status priority milestone component version severity resolution keywords cc 544 Simultaneous multiple VPNs cause route command failure yurivict "From the first VPN connection I am trying to connect to the other VPN. It performs the handshake ok, but breaks on an attempt to add routes. It turns out that OpenVPN adds such routes: 0.0.0.0/1 128.0.0.0/1 in order to introduce the new GW on top of the existing one. The second VPN tries to repeat the same and fails. The second process should understand that new GW has been already added, and should add the next best available option: 0.0.0.0/2 64.0.0.0/2 128.0.0.0/2 192.0.0.0/2 And so on and so forth, it will be reasonable to be able to do this this at least up to 3-4 (/1 .. /4). Another very bad problem is that when the second connection failed, it left it in non-functional mode. When I pressed Ctrl-C, the second connection still went ahead and deleted these two gw bypass routes, which it didn't create. And this rendered the first VPN connection unusable. So there are three problems: 1. GW bypass route should choose the best available option, up to ~/4 2. VPN shouldn't tolerate failure of 'route' command, and should dismantle VPN altogether since it isn't functional anyway. So VPN should be either fully ""on"", or fully ""off"". Currently OpenVPN leaves VPN dysfunctional when route rails. 3. OpenVPN process should never attempt to delete routes it did not create " Bug / Defect closed major Generic / unclassified OpenVPN 2.3.6 (Community Ed) Not set (select this one, unless your'e a OpenVPN developer) worksforme