[NTLUG:Discuss] Troubleshooting a network connection - fixed

[Burton Strauss]

1, 2) The enumeration is a hardware function - the OS asks the bus what's
out there and works with whatever is reported.

You can see it in the dmesg output, but unfortunately, various drivers
do/don't report things the same way.  For example:

3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0a.0: 3Com PCI 3c905 Boomerang 100baseTx at 00019800. Vers LK1.1.19
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
e100: eth1: e100_probe: addr 0xd7000000, irq 5, MAC addr 00:03:47:B1:62:26
e100: eth2: e100_probe: addr 0xd6000000, irq 11, MAC addr 00:03:47:B1:62:27

It found my 3c905 at 0a.0 on the bus (first), then found the Pro/100 dual.
So that's eth0, 1 and 2.  Note that only the 3c905 reports the bus address
but doesn't report the ethx assignment.


3) I've never found any docs - always had to read through the ifup script
and it's children to find what is being processed.


-----Burton



-----Original Message-----
From: Discuss-bounces at ntlug.org [mailto:Discuss-bounces at ntlug.org] On Behalf
Of LEROY TENNISON
Sent: Thursday, May 11, 2006 12:08 AM
To: discuss at ntlug.org
Subject: [NTLUG:Discuss] Troubleshooting a network connection - fixed

<snip />

 This raises a couple of questions:
 
 How does Linux decide which NIC is going to be eth0, eth1, and so on?
 
 How do I tell what driver is being used for eth0 and eth1.  'ifconfig'
gives me the hardware address and IP configuration but doesn't tell me what
driver.
 
 Anyone know where the format of ifcfg-eth0, ifcfg-eth1 and so on is
documented?
 
 Thanks for the help.
 
_______________________________________________
http://ntlug.pmichaud.com/mailman/listinfo/discuss