Hello there,

I have an openvpn setup that I can start manually (/etc/init.d/openvpn
start client) and works nicely. Trying to start it through nm fails to
bring up the correct routing table. When not using the applet the openvpn
server pushes a route which adds the remote network to tap0 (the vpn server is
set to bridge into the remote network) addn the routes to get to the vpn
server through the default gateway. No fancy confguration here (no
redirect-gateway or so). nm instead brings the same routing as above, but
then the default gateway got removed probably replaced by
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 tap0
which doesn't work of course. In the logs I found

 nm-openvpn[26947]: ERROR: Linux route add command failed: shell command
 exited with error status: 7

and then upon disconnection

 nm-openvpn[26947]: ERROR: Linux route delete command failed: shell
 command exited with error status: 7

but there is no more information so I'm not sure which route is failing.

cheers,
graziano

Hi All,

I also have this issue.

Routing table before connection:

192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.7.3     0.0.0.0         UG    0      0        0 eth0

Here is the routing table after a successful connection using init.d/openvpn
start

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
10.254.0.5      0.0.0.0         255.255.255.255 UH    0      0        0 tun0
10.254.0.1      10.254.0.5      255.255.255.255 UGH   0      0        0 tun0
192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.1.0     10.254.0.5      255.255.255.0   UG    0      0        0 tun0
0.0.0.0         192.168.7.3     0.0.0.0         UG    0      0        0 eth0

Here is the routing table after stopping openvpn and initiating through nm

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
87.194.103.103  192.168.7.3     255.255.255.255 UGH   0      0        0 eth0
192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0
wlan0
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 tun0
0.0.0.0         0.0.0.0         0.0.0.0         U     1000   0        0
wlan0

Also, the dns settings don't get pushed through with nm.

Thanks in advance for any help.

Kind Regards,

Thomas Greenwood

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
trying to connect to openvpn server. under kernels 2.6 and 3.0 starting openvpn from command line sets up vpn correctly with the right routes. but starting the vpn connection from network-manager-KDE connects but the routing table is wrong. I have tried to set the use route for resources on this network only to no avail. on Kernel 3.1 it connects from nm and from command line but both fail to set the correct routing table. not sure if it is related

* What exactly did you do (or not do) that was effective (or
     ineffective)?
please see aboce
   * What was the outcome of this action?
please see aboce
   * What outcome did you expect instead?

*** End of the template - remove these lines ***

After upgrading from 0.9.0 to 0.9.2 in testing I could not connect to
the internet
if the VPN was active.
I noticed the default route on the VPN machine was changed to the VPN
gateway.
After enabling the 'Use this connection for resources on the network'
Internet was
reachably again.

The server has not 'redirect-gateway def1' enabled.

Greetings,
Willem

I can confirm that this problem still persists with latest version in
Jessie (0.9.10.0-1).

Workaround Willem van den Akker suggested (enabling the "Use this
connection for resources on the network") worked perfectly in my case.

Thus, I propose that Maintainer of this package makes this option enabled
by default.


Regards,

Adnan