Gutsy beta renumbers ethernet interfaces after boot

[Nick Moffitt]

After installing 7.10-beta-amd64-alternate on an HP Proliant DL385 G2, and working around already-filed video bugs, I came across a problem with the network interfaces.

During the install, networking worked just fine, and the system was able to determine a likely hostname from the reverse DNS for its IP. It configured eth0 and had eth1 on the side. But on boot, I found that networking didn't work and the interfaces were now eth2 and eth3.

Looking in /etc/udev/rules.d/70-persistent-net.rules I now see many bogus-looking entries for eth0 and eth1, and correct entries for eth2 and eth3. Screenshot to follow (apologies in advance, as I'm doing this over a remote KVM switch).

[Nick Moffitt (nick-moffitt)]

Here's a screen capture of me catting the erroneous udev rules file

[Nick Moffitt (nick-moffitt)]

I have removed the somewhat empty eth0/1 entries, and changing the eth3 entry to map onto eth0 restored networking functionality.

[Chris Jones (cmsj)]

I have just done a test install on an IBM xSeries 345 server with two Intel PRO/1000 cards and see exactly the same thing.

[Niels (niels-gruppenkasper)]

I got the exact same behavior on my DELL 1850. Networks cards are two Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05).

After delete the entries for eth0/eth1 and changing eth2/eth3 network functionality is restored.