network manager openvpn dhcp error

[Erki Hallingu]

Binary package hint: network-manager-openvpn

When starting openvpn connection it connects ok, but after about 10 seconds it starts to query for ip address via dhcp and consequently loses it's ip address which it got from openvpn server.

Also it creates under the wired connection tab "Auto tap0" connection which has dhcp selected. It seems that this is the source of this problem.

It also happens when starting openvpn connection manually not from nm-applet.

As a result it is not possible to use network manager with openvpn. I'm only able to connect to openvpn by inserting eth0 and tap0 interfaces into /etc/netwok/interfaces file.

root@ubuntu:/etc/network# lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

Package: network-manager
Priority: optional
Section: net
Installed-Size: 2044
Maintainer: Ubuntu Core Dev Team <email address hidden>
Original-Maintainer: Riccardo Setti <email address hidden>
Architecture: amd64
Version: 0.7~~svn20081018t105859-0ubuntu1

Package: network-manager-openvpn
Priority: optional
Section: universe/net
Installed-Size: 1076
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-Maintainer: Soren Hansen <email address hidden>
Architecture: amd64
Version: 0.7~~svn20081015t024626-0ubuntu1

[Erki Hallingu (erkiha)]

installed latest network-manager from ppa and still got same issue:

openvpn connects OK but after few seconds nm creates Auto tap0 connection under wired tab and starts querying ip via dhcp which kills ip already assigned to tap0 by openvpn server.

I was able to overcome this by adding

iface tap0 inet dhcp

line to /etc/network/interfaces file so nm does not manage tap0. (It still creates one but it does not start dhcp query on it)

[bq (balique)]

I can confirm this on jaunty current (I enabled repositories 'unsupported updates, etc. ..... in adept):

versions installed :

network-manager 0.7-0ubuntu1
network-manager-kde 1:0.7svn864988-0ubuntu5

For me, adding the 'iface tap0 inet dhcp' does not solve the problem (only restarting nm after is not enough?).

[bq (balique)]

Forgot to say : In intrepid it is ok.

[bq (balique)]

Sorry for dispersed comments, next time I will think twice and write once :)

The "iface tap0 inet dhcp" workaround is now functional here too - a complete restart was needed. But I consider this not a solution, but really a workaround.

Have a nice day, bq

[Erki Hallingu (erkiha)]

Seems to be fixed with latest jaunty updates (from 2009-03-05)

[bq (balique)]

I can confirm, that it looks ok now. Thank you.