network-manager breaks static configuration

happens to me too.
i have two network cards (same card, same chipset, same driver so it's not a kernel issue).
one (eth1) is dhcp connected to the internet, and it's coming up after boot.
the other one (eth0) is static IP for my local network (i'm doing NAT) and this one used to come up, and is not coming up anymore after boot.

if i do "ifconfig -a" after boot,
the interface which does not come up is missing the line with "inet addr:" and "Bcast:" and "Mask:".
if at that point I do "sudo ifup eth0", i get "ifup: interface eth0 already configured".

config of the network cards is in /etc/network/interfaces

and is (appart from the loopback config):
iface eth1 inet dhcp
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
auto eth1
auto eth0

I did not change that config in a long long time.

if i type after boot:
sudo ifdown eth0 && sudo ifup eth0

the following is displayed:
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2

and then eth0 is up and the "inet addr", "Bcast", "Mask" appear in the "ifconfig -a" output.

maybe not connected, but in my /var/log/boot there is this line:

Mar 3 08:35:07 rcS: /etc/rcS.d/S40ifrename: 19: /sbin/ifrename: not found

looked at the packages which i upgraded, the cause of the problem might be the recent "upstart" upgrade, but it's just a guess...

the ifrename error appears unrelated:
https://launchpad.net/ubuntu/+source/update-manager/+bug/46817

Emmanuel Touzery wrote:
> looked at the packages which i upgraded, the cause of the problem might
> be the recent "upstart" upgrade, but it's just a guess...
>
If it helps, I have listed the packages I updated when my internet went out.

Commit Log for Wed Mar 14 08:31:22 2007

Upgraded the following packages:
acpid (1.0.4-5ubuntu5) to 1.0.4-5ubuntu6
app-install-data (0.3.26) to 0.3.27
apt (0.6.46.4ubuntu8) to 0.6.46.4ubuntu9
apt-utils (0.6.46.4ubuntu8) to 0.6.46.4ubuntu9
gnome-icon-theme (2.18.0-0ubuntu1) to 2.18.0-0ubuntu2
kubuntu-desktop (1.29ubuntu1) to 1.30
language-pack-en (1:6.10+20061019) to 1:7.04+20070313
language-pack-en-base (1:6.10+20061019) to 1:7.04+20070313
language-pack-kde-en (1:6.10+20061019) to 1:7.04+20070313
language-pack-kde-en-base (1:6.10+20061019) to 1:7.04+20070313
libcairo2 (1.3.14-0ubuntu1) to 1.4.0-0ubuntu1
libgnomevfs2-0 (1:2.18.0-0ubuntu1) to 1:2.18.0.1-0ubuntu1
libgnomevfs2-common (1:2.18.0-0ubuntu1) to 1:2.18.0.1-0ubuntu1
libgtk2.0-0 (2.10.9-0ubuntu2) to 2.10.10-0ubuntu1
libgtk2.0-bin (2.10.9-0ubuntu2) to 2.10.10-0ubuntu1
libgtk2.0-common (2.10.9-0ubuntu2) to 2.10.10-0ubuntu1
libnm-util0 (0.6.4-6ubuntu2) to 0.6.4-6ubuntu3
libvte-common (1:0.16.0-0ubuntu1) to 1:0.16.0-0ubuntu2
libvte9 (1:0.16.0-0ubuntu1) to 1:0.16.0-0ubuntu2
network-manager (0.6.4-6ubuntu2) to 0.6.4-6ubuntu3
synaptic (0.57.11.1ubuntu11) to 0.57.11.1ubuntu12

I also noticed that my internet, even when I connect after boot up, is
dropping out every hour or so now. I have not timed it, but it haves
happen to me twice now.

OK, based on the list of packages provided by Scott Lewin, I uninstalled network-manager, network-manager-gnome and ubuntu-desktop (since ubuntu-desktop depends on network-manager) from my computer, rebooted and... the network interface is coming up fine!
i tried to reboot a second time, once more it worked OK. Then I reinstalled it and it doesn't work again.
So the problem comes from network-manager.

Emmanuel Touzery wrote:
> OK, based on the list of packages provided by Scott Lewin, I uninstalled network-manager, network-manager-gnome and ubuntu-desktop (since ubuntu-desktop depends on network-manager) from my computer, rebooted and... the network interface is coming up fine!
> i tried to reboot a second time, once more it worked OK. Then I reinstalled it and it doesn't work again.
> So the problem comes from network-manager.
I also uninstalled network-manager, which also uninstalled
knetwork-manager, and I got the exact same results. My connection
connected as normal on startup without problem.

The question I have is, what does network-manager do?

I believe we should also change the affected program on this bug to
network-manager.

I don't understand why there is no reaction from developers to this bug.
That at least some configurations with static IPs don't work anymore in feisty, with apparently no other workaround that deinstalling network-manager seem like a serious problem to me.
Also the fact that it worked with 0.6.4-6ubuntu2 and not anymore with 0.6.4-6ubuntu3 should help to narrow the problem.

The changelog for ubuntu3 version was:

   * Manage some static devices we can understand. This should avoid the
     problem people are having with NM marking the machine as offline when
     it's just on static instead. LP #82335.

So obviously that change made network-manager decide to manage some devices that it clearly cannot understand, since the connection is down when it should be up.

anyway, i think that this bug in a final release would be quite bad.

When I plug in my USB wifi adapter (configured in e-n-i) I can see from its LED that it connects for a second, and then looses it again. When I stop network-manager, it works fine.

I have added this two lines to rc.local:

ifdown ra0
ifup ra0

and by doing just that the connection works after boot and doesn't fail anymore (and knetworkmanager doesn't break it).

I don't know if I should add this here or in a new bug.

When I start knetworkmanager (using a network defined in /etc/network/interfaces, not in knetworkmanager), it doesn't realize I'm already "connected" (KWifiManager does) and then KDE applications (like kweather, kopete) start behaving like there's no connection. When I close knetworkmanager, they go back to normal.

Just want to add that I do not have a static IP address, but a static configuration like in the original report. It seems like network-manager wrongly wants to take control of all interfaces with dhcp and auto, even if I have configured wireless-essid and wireless-key for it (and network-manager does not work with my kind of wifi card).

I've checked src/backends/NetworkManagerDebian.c and indeed, my interface is not blacklisted by nm_system_device_get_disabled.

I'm seeing this too, I have a usbnet connection to my PDA that until ubuntu3 was ignored by NM. Now NM tries to bring it up, and annoyingly tries to use it as the default route.

Me too!!!

this is a fresh Festy install (Beta). After installation, I had a working DHCP lease.
I wanted a static adres, so I use network-manager to alter the settings.
That did not work!!

I removed network-manager, things did not get any better.

Whe I switch eth0 back to dhcp, that does not work anymore also.

I do not regard myself a novice, but I'm completly lost.

I've got (or had got) this problem too, with upgrading a machine 100km away from me, so it was quite uncomfortable problem :) See Bug #105393 if interested.

<quote>Me too!!!

this is a fresh Festy install (Beta). After installation, I had a working DHCP lease.
I wanted a static adres, so I use network-manager to alter the settings.
That did not work!!

I removed network-manager, things did not get any better.

Whe I switch eth0 back to dhcp, that does not work anymore also.

I do not regard myself a novice, but I'm completly lost.</quote>

Yup, exactly the same here. Everything broke since having tried setting a static addr.

Indeed 0.6.4-6ubuntu3 broke things, but they were fixed in

network-manager (0.6.4-6ubuntu5) feisty; urgency=low

  * Partially revert 0.6.4-6ubuntu3, but if we find interfaces which are
    disabled, we assume we are always online to avoid trouble when people
    have advanced and semi-advanced setups.

 -- Tollef Fog Heen <email address hidden> Mon, 9 Apr 2007 21:39:20 +0200

Can you please upgrade to the latest Feisty packages and check again?

Just updated my Kubuntu Fiesty and knetwork-manager still does not work. Everything is current as of now.

Mike

well i tried to reinstall network-manager and network-manager-gnome now, and i can confirm: for me it works with the latest packages even though it was broken with -ubuntu3.
so for me the bug is fixed.

well..... I just installed the fresh feisty RC (20070415)..... I configured to use the static IP, the info correct... it works for the first few minutes, afterwards it just doesn't work anymore......

mikeh, since there are a lot of different people with different setups here, can you please give an updated description of your situation? How does your /etc/network/interfaces look like (attach it, please), how does n-m behave now?

Release-noted, so milestoning for post-Feisty.

Several different machines setup. 4 desktops with feisty currently updated. Using belkin usb 802.11b net adapters. Recognized as wlan0. These adapters were recognized and worked great using knetworkmanager up untill I reported this problem. On that day theupdate broke it.

Main machine is a dell D820 laptop, using Intel 3945. Recognized as eth1. Again it worked great untill that update. I don't know if it was a n-m update or knetworkmanager that broke it?
Here is teh /etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet static
address 192.168.14.107
netmask 255.255.255.0
gateway 192.168.14.1

auto eth1
iface eth1 inet static
wireless-essid linksys
address 192.168.14.113
netmask 255.255.255.0
gateway 192.168.14.100

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

I have made no changes to this file, and have not used any static setups. Now in order to get any net to work I use ifconfig, iwconfig, and dhclinet in console. None of the net adapters are recognized by knetworkmanager. The system is up to date as of today.

Interestingly I have another laptop I use for screen projection at the church. When the updates broke all these other machines I stopped updating it so it still works great!

Hope this helps us figure it out!

Mike

micah, can you please elaborate what you mean by 'broken'? It is deliberate that eth1 is not present in network-manager, because you have a static configuration for it. eth2, ath0, and wlan0 should appear and work, though.

Hi,

I would like to report that my problems are resolved.

Gert-Jan Braas

anyone can confirm that this bug is (not-)gone in gutsy?

 - Alexander

Not gone for me.
Sorry I opened another bug, but I was on another trail (avahi):
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/138895

I just found the bug here related to network-manager. Gusty up to date.

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]