network-manager-vpnc resolvconf conflict
Bug #183585 reported by
Dan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-vpnc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-
The vpnc plugin for network-manager wasn't updating /etc/resolv.conf although running vpnc from the CLI worked just fine. Numerous forums report the same issue. I found the resolution here:
http://
The following fixed it for me:
sudo apt-get remove resolvconf
resolvconf is installed by default at least on my Gutsy system
To post a comment you must log in.
I have found the culprit: /etc/resolvconf /update. d/libc, the script that takes the information from resolvconf and actually updates /etc/resolv.conf, is limited to three name servers. It takes information from the files in /etc/resolvconf /run/interface/ , reading them in order as they are returned by /lib/resolvconf /list-records. This order is configured in /etc/resolvconf /interface- order. NetworkManager uses /etc/resolvconf /run/interface/ NetworkManager, which has a surprisingly low priority -- it is caught by the "*" at the end of interface-order.
The fix, without removing resolvconf, is to add "NetworkManager" on a new line to /etc/resolvconf /interface- order right after the comment. resolvconf and its scripts will now take NetworkManager's opinion much more seriously than all the others'.