How to stop NetworkManager from frobbing my /etc/resolv.conf
mrsam at courier-mta.com
Sun Sep 26 16:49:41 UTC 2010
After copiously scouring links all over the place, I think that I've
succesfully managed to set up a bridge between my real network interface and
the virtual network interface used by virtmanager-hosted virtual machines. I
now have F13 hosting a virtualized machine with full network connectivity.
One glitch remains that I can't fix. After a reboot, /etc/resolv.conf has
nothing useful, even though dhclient came up fine on the bridge.
Experimentation uncovered NetworkManager as the guilty party.
NetworkManager, AFAIK, doesn't know anything about virtual bridges. I had to
set it up by hand:
[root at monster network-scripts]# cat ifcfg-vnet0
eth0 is bridged:
[root at monster network-scripts]# cat ifcfg-eth0
# Intel Corporation 82573E Gigabit Ethernet Controller (Copper)
[ bunch more stuff snipped ]
I also have eth1, which I would like to be owned by NetworkManager:
[root at monster network-scripts]# cat ifcfg-eth1
# Intel Corporation 82573L Gigabit Ethernet Controller
What's happening is this. The S10network script runs first, and brings up
eth0 than vnet0; and configures the interface and /etc/resolv.conf from
DHCP. Later S23NetworkManager runs, and removes my DNS server from
resolv.conf, because none of the NetworkManager-owned network interfaces are
I want to use NetworkManager for eth1, but I'll have to either disable it,
or bounce the network initscript after NetworkManager, which might cause
some confusion elsewhere.
Is there a way to force NetworkManager not to touch /etc/resolv.conf.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100926/6696e805/attachment.bin
More information about the users