public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: girish@bombay.retortsoft.com, linux-kernel@vger.kernel.org
Subject: Re: how to map network cards ?
Date: Mon, 31 Dec 2001 10:32:13 -0600 (CST)	[thread overview]
Message-ID: <200112311632.KAA51999@tomcat.admin.navo.hpc.mil> (raw)

Girish Hilage <girish@bombay.retortsoft.com>:
> 
> Hello everybody,
> 
>  This is my first mail to the list. I want to know, what /sbin/lspci outputs are nothing but the contents of '/proc/bus/pci/devices' in a readable form?
> 
>  And if so how do I know which entry implies which network interface (e.g. eth0, eth1 etc.)?

You don't.

There is no fixed method, though the following may help:

1. eth0 is assigned to the first device identified. This works if you have
   multiple interfaces (using different drivers), then the order the drivers
   are loaded will define which is eth0 - I do this for a system with
   mixed 3c509 (ISA), and 3c905 (PCI) interfaces.
2. In a muli-interface environment with (say) two 3c509 - the order happens
   to be in bus order. This has implied that the slot number it is plugged
   in determines which is eth0. In my case a system has two PCI 3c905C
   interfaces, the first at 00:0e.0, and the second at 00:0f.0. The 0e.0
   interface appears as eth0.

Note: if one of the interfaces is unplugged/fails dramatically , the bus scan
will assign the FIRST interface located as eth0. The only way to determine
the ACTUAL eth0 is via mac number and trial and error.

I configure ONE interface (all others are down), then plug in to a working
network.

If I can ping the other machine then I know which network a given
interface is on - label it.

Now down that interface, and initialize another one. Repeat until all
interfaces are identified.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-12-31 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31 16:32 Jesse Pollard [this message]
2001-12-31 16:40 ` how to map network cards ? Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-12-31 17:34 Jesse Pollard
2001-12-31 17:41 ` Jeff Garzik
2001-12-31 15:54 Girish Hilage
2001-12-31 16:20 ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200112311632.KAA51999@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=girish@bombay.retortsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox