From: Bill Davidsen <davidsen@tmr.com>
To: andreas.hartmann@fiducia.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: distinguish two identical network cards
Date: Mon, 23 Feb 2004 11:33:45 -0500 [thread overview]
Message-ID: <403A2B69.2070508@tmr.com> (raw)
In-Reply-To: <OF0D5B57F7.B29B3783-ONC1256E43.0035BF41@fiducia.de>
andreas.hartmann@fiducia.de wrote:
> Hello!
>
> Some clarification:
> It is important, that the cards can be distinguished without any user driven
> action - it must run automatically. The machines will be delivered to somebody
> who doesn't know anything about linux / unix. I must be able to do a
> configuration like that:
>
> Physical upper card: eth0
> Physical lower card: eth1
>
> The customer will be told, e.g.: plug in the network cable from switch a to the
> upper card, the cable to the switch b must be connected to the lower card.
Sorry, other than the already suggested use of nameif I don't see any
other good way to do it. At some point the hardware should pass through
the hands of someone who DOES know Linux enough to read the MAC address
off the sticker usually found on the NIC, and set the config to match.
You better label the back of the NICs, if your customer can't identify
the one with the blinking light (as previously suggested) they may have
problems with UNIX terms like upper and lower ;-)
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2004-02-23 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 9:53 distinguish two identical network cards andreas.hartmann
2004-02-23 16:33 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 8:49 andreas.hartmann
2004-02-23 9:07 ` Krishnakumar. R
2004-02-23 10:35 ` Toon van der Pas
2004-02-23 9:32 ` Micha Feigin
2004-02-23 22:51 ` Karl Tatgenhorst
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=403A2B69.2070508@tmr.com \
--to=davidsen@tmr.com \
--cc=andreas.hartmann@fiducia.de \
--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