Red Hat Bugzilla – Bug 107376
kernel 2.6.0-0.test7.1.57smp reversed ethernet device scan (e1000)
Last modified: 2007-04-18 12:58:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
On a system with 2 ethernet interfaces (e1000 driver), the names eth0 and eth1
have exchanged their meaning (compared to 2.4.20-8).
The physical interface which used to be eth0 is now called eth1, and vice versa.
This makes the network configuration cumbersome if you want to switch kernels.
In our example, the interface in PCI slot 03:07.0 (IRQ 30), with the MAC address
00:07:E9:04:52:3E was called eth1 in 2.4.20-8.
The interface in PCI slot 03:07.1 (IRQ 31), MAC 00:07:E9:04:52:3F was called
eth0 in 2.4.20-8.
In 2.6.0-0.test7.1.57smp the names eth1 and eth0 are inverted.
Is this a bug or a feature?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.check network interfaces in 2.4.20-8
3.check network interfaces again.
Actual Results: eth0 Link encap:Ethernet HWaddr 00:07:E9:04:52:3E
eth1 Link encap:Ethernet HWaddr 00:07:E9:04:52:3F
Expected Results: eth0 Link encap:Ethernet HWaddr 00:07:E9:04:52:3F
eth1 Link encap:Ethernet HWaddr 00:07:E9:04:52:3E
Created attachment 95267 [details]
actual results for 2.6.0-0.test7.1.57smp
Created attachment 95268 [details]
expected results (2.4.20-8smp)
Sorry, I should have read http://www.codemonkey.org.uk/post-halloween-2.5.txt
before submitting this issue...:
- Users of boxes with >1 NIC may find that for eg, eth0 and eth1 refer to
the opposites of what they did in 2.4. This is a bug that will be fixed
before 2.6.0. One option (or management workaround) for this is to use
'nameif' to name Ethernet interfaces. There is a HOWTO for doing this at
Problem is fixed in 2.6.0-0.test11.1.99smp