From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: jgarzik@mandrakesoft.com,
Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: girish@bombay.retortsoft.com, linux-kernel@vger.kernel.org
Subject: Re: how to map network cards ?
Date: Mon, 31 Dec 2001 11:34:08 -0600 (CST) [thread overview]
Message-ID: <200112311734.LAA43032@tomcat.admin.navo.hpc.mil> (raw)
--------- Received message begins Here ---------
>
> Jesse Pollard wrote:
> > The only way to determine
> > the ACTUAL eth0 is via mac number and trial and error.
>
> not correct, as noted in other e-mail.
>
> > 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.
>
> also note that one can rename interfaces, or in the future they might
> appear out-of-order. To only way to be obsolutely certain where a
> network device is on the PCI bus is ETHTOOL_GDRVINFO.
>
> Jeff
Does ETHTOOL_GDRVINFO work on ISA devices too? Last I knew it didn't. And
I do run a system with both PCI and ISA network cards.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-12-31 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 17:34 Jesse Pollard [this message]
2001-12-31 17:41 ` how to map network cards ? Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-12-31 16:32 Jesse Pollard
2001-12-31 16:40 ` 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=200112311734.LAA43032@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=girish@bombay.retortsoft.com \
--cc=jgarzik@mandrakesoft.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