routes are incorrectly configured to tap0 instead of eth0 interface

Bug #452186 reported by bikeridercz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-openvpn (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager-openvpn

Dear all,

I'm trying to add some routes to my OpenVPN configuration in NM. After connecting to VPN routes are set but does not work because they are bound to wrong interface "tap0", output from route command follows ...

10.33.17.0 10.32.90.1 255.255.255.0 UG 0 0 0 tap0

So, I have to add routes manually by "route add" command, then it work well ... The only difference is interface where they are bouded to as you can see ...

10.33.17.0 10.32.90.1 255.255.255.0 UG 0 0 0 eth0

Please help,

Thanks and regards.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia wl
Package: network-manager-openvpn 0.7.1~rc4.1.20090323+bzr27-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-openvpn
Uname: Linux 2.6.28-15-generic i686

Revision history for this message
bikeridercz (rmkk) wrote :
Revision history for this message
Adrian Bridgett (adrian-bridgett) wrote :

try editing the vpn setting:
IPv4 Settings -> Routes -> Use this connection only for resources on its network (enabled)

That should do what you want (I'm not sure why this is being forced on - the VPN itself doesn't ask for the route to be added).

I'm still fighting some more issues myself with VPN via NM so this may not be the correct answer!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.