Bug 761313

Summary: NetworkManager continually clobbering /etc/resolv.conf
Product: [Fedora] Fedora Reporter: Jeff Layton <jlayton>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 16CC: dcbw, steved
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-02 23:36:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
last 1000 lines in /var/log/messages none

Description Jeff Layton 2011-12-08 02:29:07 UTC
Created attachment 542334 [details]
last 1000 lines in /var/log/messages

I have VPN access set up through NetworkManager. I also have a dispatcher.d script set up like this:

----------------------------[snip]---------------------------
#!/bin/bash

if [ "$2" = "vpn-up" ]; then
	cp /etc/resolv.conf /etc/resolv.conf.nm
	/sbin/service dnsmasq start
	cp /etc/resolv.conf.dnsmasq /etc/resolv.conf
fi

if [ "$2" = "vpn-down" ]; then
	cp /etc/resolv.conf.nm /etc/resolv.conf
	/sbin/service dnsmasq stop
fi
----------------------------[snip]---------------------------

resolv.conf.dnsmasq points the resolver at localhost. This generally works fine, and has worked for several Fedora releases. Recently though, it has stopped working consistently.

When I first start the VPN everything is fine, but within a few minutes (5-10) resolv.conf is overwritten with the DNS settings that the DHCP server provides. This causes DNS access on the VPN to stop functioning properly.

I'll also note that NetworkManager has become extremely chatty with syslog. A sample from /var/log/messages is attached.

NM package versions:

NetworkManager-glib-0.9.2-1.fc16.x86_64
NetworkManager-openconnect-0.9.0-3.fc16.x86_64
NetworkManager-gtk-0.9.2-1.fc16.x86_64
NetworkManager-pptp-0.9.0-1.fc16.x86_64
NetworkManager-openvpn-0.9.0-1.fc16.x86_64
NetworkManager-vpnc-0.9.0-1.fc16.x86_64
NetworkManager-gnome-0.9.2-1.fc16.x86_64
NetworkManager-0.9.2-1.fc16.x86_64

Comment 1 Jeff Layton 2011-12-08 02:46:17 UTC
Downgrading these packages seems to have resolved the problem for now, and quieted down the logging too:

NetworkManager-glib-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-gnome-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-gtk-0.9.1.90-5.git20110927.fc16.x86_64
NetworkManager-0.9.1.90-5.git20110927.fc16.x86_64

...let me know if you need any other info.

Comment 2 Jeff Layton 2011-12-22 00:41:05 UTC
Raising sev/pri to high. Still unresolved after 2 weeks, and is a clear regression.

Comment 3 Jeff Layton 2012-02-02 23:36:07 UTC

*** This bug has been marked as a duplicate of bug 782175 ***