[gutsy] Network interface don't work anymore

[LCID Fire]

Binary package hint: network-manager

After upgrading to gutsy my network interfaces don't work anymore.
Manually trying to start networking gives me:

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth1.
Ignoring unknown interface eth2=eth2.

[Alexander Sack (asac)]

please attach your /etc/network/interfaces and /etc/network/interfaces.bak-* files to this bug.

Thanks,

  - Alexander

[LCID Fire (lcid-fire)]

Since my hald and networking is not working - I'll just write the content.
interfaces:

auto lo
iface lo inet loopback

auto eth1

iface eth1 inet dhcp

iface dsl-provider inet ppp
provider dsl-provider

auto eth2

iface eth0 inet dhcp

[LCID Fire (lcid-fire)]

And interfaces.bak-0:

auto lo
iface lo inet loopback

auto eth1

iface eth1 inet dhcp

iface dsl-provider inet ppp
provider dsl-provider

iface eth2 inet dhcp

auto eth2

[LCID Fire (lcid-fire)]

The eth1 and eth2 interfaces where from back in the days when I had another mainboard with multiple network interfaces. So i cleaned up interfaces and iftab and now only have a interfacescontaining:
auto lo
iface lo inet loopback

auto eth0

iface eth0 inet dhcp

And it works like a charm :)
Strange thing is - this worked in feisty so I fear that gutsy got a little more picky about messed up configurations.

[Alexander Sack (asac)]

gutsy network manager will not manage auto dhcp interfaces anymore. The idea is that you have no interface configured at all in /etc/network/interfaces, maybe test that as well.

Thanks,
  - Alexander

[earthforce_1 (earthforce1)]

I am seeing this too - happened recently with the last update. Backstepping to an earlier kernel (-12) did not help,

[earthforce_1 (earthforce1)]

Addendum - found a rather strange workaround for it - plugged the network card into a wireless bridge with a fresh IP address and rebooted, and it seemed to take. Maybe something is being cached? Ran into this with two different PCs and the rather strange workaround saved me in each case.