Sounds like the issue is known and acknowledged enough that further proof of it's existence isn't needed but just for the record the same thing happens to me.
Desktop machine in my case which I don't believe was originally using nm. It definitely always had a static ip, (I occasionally use it to reach the machine from outside.) Unfortunately as this is just a desktop I pay very little attention to it and I don't remember the exact history and can't say exactly what I did originally and what I did subsequently and what changed when it wasn't supposed to over the last couple years. I can't say for sure that I didn't use nm to configure the static ip. I just know that since the in-place upgrade, nm wipes out resolv.conf every boot and the box can not resolve names until I rewrite it, and for some reason the nic was renamed from eth1 to eth2 and there is no eth 1 or 0. nm displays two connections "ifupdown (eth1)" , and "Auto eth2". eth0 is not displayed anywhere but references to it still exist in config files. I'm pretty sure eth0 was a physically different nic that was replaced long ago. No hardware change of any sort happened before, during or after the dist upgrade. Physically there is only one nic ifconfig -a shows only eth2, lo, and vboxnet0 /etc/network has: interfaces: ---tof--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth1 inet static address 10.0.0.80 netmask 255.255.255.0 gateway 10.0.0.208 auto eth1 ---eof--- interfaces.bak-0 ---tof--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp ---eof--- I never manually edited those files. I didn't even know that's where ubuntu stored such things until reading this thread. (I only use ubuntu on a few desks and portables, my servers are all opensuse, so when it comes to the types of machines I use ubuntu on, I am pretty much like any illiterate user, or at least I _want_ to be.) Digressing but while writing this, I disabled networking from the gnome network manager taskbar applet, and and now, for the life of me I can not figure out how to re-enable it (without going behind the scenes and manually running ip or ifconfig & route as root) System > Preferences > Network Connections displays the connections (a bogus eth1 and the new eth2) and lets me edit the ip settings, but does not activate the connection, even when toggling the connect-automatically box. What is a regular user supposed to do, reboot? Logout of gnome & back in? Never ever touch that disable button that's sitting there so easy to press? Why doesn't the thing that looks like it's supposed to operate the network connections do so? Or if it actually does, then why couldn't a person who knows how to do it the "hard" way with ip/ifconfig/route (in any number of unix and unix-like OS's btw) figure it out? That has to be one of those hundred annoyances... -- [karmic] n-m overwrites /etc/resolv.conf even when NICs are configured in /etc/network/interfaces https://bugs.launchpad.net/bugs/435618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
