© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Using Hardy on AMD64.
To me it looks as though the DNS handling of kvpnc (or openvpn?), NetworkManager and resolvconf do not really go well together.
Case 1: kvpnc, openvpn, NetworkManager, but NO resolvconf:
I can open a VPN connection and everything works fine for some minutes. After some minutes, however, /etc/resolv.conf is overwritten by the default nameserver (I assume by NetworkManager), so that the VPN nameservice doesn't wokr anymore.
Case 2: kvpnc, openvpn, NetworkManager and resolvconf:
NetworkManager uses resolvconf (by way of the ifup-scripts, if I'm not mistaken), however kvpnc does not - it simply overwrites /etc/resolv.conf and saves a copy of the old one. When /etc/resolv.conf is reinstalled by kvpnc after the VPN has been disconnected, it copies the old version of resolv.conf over the kvpnc-version. However, as resolvconf requires a symbolic link, this will destroy the functionality of resolvconf...
Does anybody know how to get kvpnc to use resolvconf? That would probably be the best solution...