multiple network interfaces -> getting card vendor for eth0...

linen0ise · 12-07-2003, 01:17 PM

hi ^^
sorry if this question is in the wrong place...
I was just wondering how I can determine which nic is eth0, which one eth1 (card name) and how to swap eth0 with eth1...if it is possible at all.
I haven't found out yet in which order or after which criteria linux assigns eth[\d] to the nic's.
thanks if anybody can help me with this one =]

Tinkster · 12-07-2003, 01:26 PM

The question is in the right place,
but your attitude [signature] stinks ...

You can resolve the issue of which is
which by using the MAC addresses,
or even the LED's (physical activity).

And you can set the order by aliasing
the drivers in modules.conf.

Cheers,
Tink

linen0ise · 12-07-2003, 01:45 PM

thanks for the answer
well thats what I usually do...but neither MAC addresses nor LED's won't be of any use because I have two cables, one labeled with '3Com' and the other one 'realtek' (not my work =] ) and the server is buried under approx. 2 tons of cable (not my work) and several other stuff and I would have to remove about 60 cables...which I won't do because there is no documentation (thats how some admins seem to make sure they keep there job ^^)
I guess there isn't a command for that ? :/

Quote:

The question is in the right place,
but your attitude [signature] stinks ...

hihi....sorry....I can't do anything about that...it's sometimes really annoying reading through ten 100p+ docs until finding the one that solves your problem =] please forgive me ^^

Tinkster · 12-07-2003, 02:11 PM

You may want to consider using the "remove
the other end of the cable from patchfield
technique", then ... you should have a fair
idea of whether you can ping or not ;)

Cheers,
Tink

vvv · 12-07-2003, 03:13 PM

Well, I think I'll field the only question that hasn't been answered yet:
Which network card gets which eth nickname?

And, in this regard, the answer is rather simple: the network card with the lowest IRQ gets eth0, the one with the IRQ higher than that gets eth1, and so on.

linen0ise · 12-07-2003, 07:39 PM

Quote:

You may want to consider using the "remove
the other end of the cable from patchfield
technique", then ... you should have a fair
idea of whether you can ping or not

stupid me *bangsheadagainstwall* ^^

thanks vvv =]

Tinkster · 12-07-2003, 07:45 PM

Quote:

Originally posted by vvv
And, in this regard, the answer is rather simple: the network card with the lowest IRQ gets eth0, the one with the IRQ higher than that gets eth1, and so on.

And there was me thinking it depended on the
number of the PCI slot they are in :}

Cheers,
Tink

vvv · 12-07-2003, 07:49 PM

Quote:

And there was me thinking it depended on the
number of the PCI slot they are in :}

Might be, might very well be. The IRQ rule has worked for me so far, but I make no claims it's 100% correct.

I'll look into it. Would you do so as well?

vvv · 12-07-2003, 08:13 PM

Whoops, had a brain fart.
You're completely correct, Tinkster.

Tinkster · 12-07-2003, 08:16 PM

Don't know how "authoritative" this is, but...

http://www.tux.org/hypermail/linux-v...-Jul/0004.html
http://support.3com.com/infodeli/too...nux/readme.txt

... it's similar to what I found on a few machines
with two interfaces.

I didn't verify though whether the interrupts
are "sticky" to the slots or not.

Cheers,
Tink

[edit]heh, you beat me to the response by three minutes ;}[/edit]