|
|
Hey folks, Any ideas. I've seen this issue a second time now. Colin Ryan wrote: > Server is 2.0.9 on Linux. > Client is 2.1rc2. > > Standard configuration that works on XP and On my Test Vista. > > But on some production machines the following occurs: > > * Yes running "Run as Administrator". > * OPVPN connects just fine, get's its IP just fine, set's routes just fine. > * Local Area IP is 192.168.2.7 > * VPN Subnets are 10.25.1.x > * Remote network is 172.21.1.0 > > BUT. > > The routes are getting assigned to the wrong Interface, i.e. the LAN > Interface not the TAP interface. > > So the routing Table ends up looking like: > > 172.21.1.0 255.255.255.0 10.25.1.5 192.168.2.7 > > where it should be and I can manually change it to be: > > 172.21.1.0 255.255.255.0 10.25.1.5 10.25.1.6 > > by deleting the first route and adding it back like > > route add 172.21.1.0 255.255.255.0 10.25.1.5 metric 2 int 16 > > where 16 is the Interface Index for the Tap Driver. > > Any idea's I've never seen this before. > > C > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Openvpn-users mailing list > Openvpn-users@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/openvpn-users > ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |