All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir B. Savkin" <savkin@shade.msu.ru>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] which NIC is which
Date: Wed, 10 Jul 2002 12:38:55 +0000	[thread overview]
Message-ID: <marc-lartc-102630499928867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102624934518788@msgid-missing>

Thus spake bert hubert:
> On Tue, Jul 09, 2002 at 02:14:05PM -0700, John Telford wrote:
> > I'm building routers.  It's difficult to tell in advance which NIC will
> > be assigned eth0 and which will assigned eth1 when using two NICs.  Ping
> > testing usually clears up this simple problem.
> > 
> > The identification problem gets worse when adding a third NIC, after
> > sorting out the first two NICs.  Frequently the eth0 or eth1 assignments
> > for the first two NICs change.
> 
> There are tricks to configure based on the MAC address of your interface
> instead of on its place in the probe. Perhaps googling on that will help.

A script to rename interfaces with "ip link ... set name ..." after
modprobe according to their hw addresses should suffice.

I never tried this because in my experience order of detection was always
consistant between reboots assuming there are no hardware chasnges.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-07-10 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 21:14 [LARTC] which NIC is which John Telford
2002-07-09 21:56 ` Arthur van Leeuwen
2002-07-09 22:06 ` Michael T. Babcock
2002-07-10  6:37 ` Arthur van Leeuwen
2002-07-10  8:34 ` bert hubert
2002-07-10 12:38 ` Vladimir B. Savkin [this message]
2002-07-10 12:42 ` bert hubert

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=marc-lartc-102630499928867@msgid-missing \
    --to=savkin@shade.msu.ru \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.