Hi all,
All our systems have multiple NICs on them. On some systems however,
Linux brings up the NICs in a different order than the BIOS orders
them. For example, the BIOS orders an on-board NIC as the first and
a PCI add-on card NIC as the second. But when Linux comes up, for
some reason it
Isn't the order they come up in determined by the order in which the
driver modules are loaded? So, say you have an on-board intel NIC
and a PCI 3com in one system and an on-board intel NIC and a PCI
tulip-based card in another, if the module load order is 3com, intel,
tulip they are of
Hmm... on second thought, if the driver module for the on-board
network and the PCI NIC are the same, I'm not sure how you would
control the order for that.
- Chris
On Aug 15, 2006, at 9:11 AM, Chris Linstid wrote:
Isn't the order they come up in determined by the order in which
On 8/15/06, Paul Lussier [EMAIL PROTECTED] wrote:
I thought there was a way to force the OS to use the same ordering,
but can't remember the details. Anyone have pointers to an
explanation?
At least on udev systems, there's an /etc/iftab file that creates a
mapping of interface name to MAC
A network interface can have any name whatsoever; the default
(dainbramaged) approach is to let the kernel pick the names,
with the result that they end up being of the form ethN where
N is the order of registration (which is roughly equivalent to
the order of HW discovery, which is roughly
This is a problem with the 2.6 kernel where it names the cards in the order
it sees them on the PCI bus.
The nameif utility in the net-tools package can be used to rename the
interfaces based on their MAC address.
nameif eth1 00:1f:33:3b:45:1a
nameif eth0 00:1f:33:3b:45:1b
You can possibly
It would depend on the prevailing mood of humantiy ;-)
http://en.wikipedia.org/wiki/Global_Consciousness_Project
Chris Linstid wrote:
Hmm... on second thought, if the driver module for the on-board
network and the PCI NIC are the same, I'm not sure how you would
control the order for
This persistent naming issue gained importance as
interconnect technologies like SCSI, FibreChannel,
USB, PCMCIA and HotPlug PCI (to name a few) made it
possible for physical configurations to change from run
to run or even on the fly. Addressing this issue was
one of the goals of udev. I