Re: eth0 - eth1 confusion vs. local network
- From: Andrei Popescu <andreimpopescu@xxxxxxxxx>
- Date: Mon, 8 Feb 2010 22:29:59 +0200
On Mon,08.Feb.10, 01:15:43, Stan Hoeppner wrote:
Perhaps the kernel brings eth1 into existence by first establishing it as
eth0, then renaming it to eth1; then bringing the "real" eth0 into
existence.
The above can happen when you add NICs to the system. I hate UDEV for this, and
it took me the better part of a day to figure this out a few months ago. UDEV
names the devices based on PCI bus slot number order. If you add a new PCI NIC
into an empty slot with a lower number than that of the NIC already in the
system, UDEV makes the lowest slot number eth0 and the higher slot number eth1.
I seem to recall such issues in the (quite distant) past.
The solution is to change the PCI slot order or create a UDEV static naming
rule based on MAC address that overrides the slot number ordering.
This is already done in /etc/udev/rules.d/70-persistent-net.rules (which
is actually generated by another rule).
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: eth0 - eth1 confusion vs. local network
- From: Stan Hoeppner
- Re: eth0 - eth1 confusion vs. local network
- References:
- Re: eth0 - eth1 confusion vs. local network
- From: Frank Miles
- Re: eth0 - eth1 confusion vs. local network
- From: Stan Hoeppner
- Re: eth0 - eth1 confusion vs. local network
- Prev by Date: Re: What does "Stale NFS file handle" mean?
- Next by Date: Re: unionfs
- Previous by thread: Re: eth0 - eth1 confusion vs. local network
- Next by thread: Re: eth0 - eth1 confusion vs. local network
- Index(es):
Relevant Pages
|
