Network Manager's openvpn plugin doesn't respect DHCP's domain setting.

[mithro]

Binary package hint: network-manager-openvpn

Network Manager's openvpn plugin ignores the "DNS Domain" setting sent. This means that it doesn't correctly updated the /etc/resolv.conf when connecting to a openvpn connection.

[mithro (mithro)]

This patch fixes the problem.

[Luca Falavigna (dktrkranz)]

Thank you for your bug report.
You should consider to send your patch to upstream developers in order to have it reviewed properly.

[mithro (mithro)]

I wasn't sure if upstream wanted the patch as they have gone in a drastically different method in there current development version.

[Philipp Kern (pkern)]

A new version of network-manager-openvpn was uploaded to fix this bug.

To review the current version, please run

  dget -x http://ppa.launchpad.net/pkern/ubuntu/pool/main/n/network-manager-openvpn/network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc

[mithro (mithro)]

The above command doesn't work.

$ dget -x http://ppa.launchpad.net/pkern/ubuntu/pool/main/n/network-manager-openvpn/network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc
dget: retrieving http://ppa.launchpad.net/pkern/ubuntu/pool/main/n/network-manager-openvpn/network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
curl: (22) The requested URL returned error: 404
dget: curl network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc http://ppa.launchpad.net/pkern/ubuntu/pool/main/n/network-manager-openvpn/network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc failed

[Daniel Holbach (dholbach)]

That's a bug in ppaput.

dget -x http://ppa.launchpad.net/pkern/ubuntu/pool/universe/n/network-manager-openvpn/network-manager-openvpn_0.3.2svn2342-1ubuntu3.dsc

[Daniel Holbach (dholbach)]

The changes look ok, but why do you switch to quilt?

Assigning package review to Søren Hansen, who maintains the package.

[Philipp Kern (pkern)]

network-manager-openvpn (0.3.2svn2342-1ubuntu3) gutsy; urgency=low

  [ Cleanup ]
  * Switched to quilt for patch management.
  * Properly activated the awk patch.

  [ Bug fixes ]
  * Increased the timeout by 5s to 15s before openvpn gets killed
    forcefully. (LP: #117992)
  * Corrected the path to `nm-vpn-properties' in the desktop file.
    (LP: #123772)
  * Pull DNS domain setting from remote OpenVPN server.
    (LP: #138181)
  * Introduced a new configuration option enabling users to turn off the
    check for a proper `nsCertType=server' extension bit set in the
    server's certificate. (LP: #94788)

  [ Philipp Kern ]
  * Fixes (LP: #145884)

 -- Philipp Kern <email address hidden> Fri, 28 Sep 2007 02:05:51 +0200

[VDR (vdr)]

Look:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/149110

I use VPN only to some adress, so I use optional configuration. I don`t set default route via VPN tunel.
My VPN servers doesn`t send a DNS settings.

So If VPN server doesn`t send a DNS settings, why network-manager delete the proper from /etc/resolv.conf ??

I have DNS in my local LAN, but not always can change VPN server config (ie. not root at VPN server).
And sometime want my DNS server as primary server, when a VPN server send DNS settings.

I think, that a good options is a choice in Optional tab: "pull DNS settings from VPN server" or not.

[serrs (serrs)]

I'm having the same problem as VDR. Apparently the patch also causes the resolv.conf to get replaced with no "server" line if the OpenVPN server does not push DNS.

I don't want my OpenVPN server to push DNS. ---> my resolv.conf gets clobbered. (with white space)

I have my OpenVPN server push DNS ---> the patch above does it's job.

From my point of view, this patch causes more problem than it fixes.