All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Kroth <bpkroth@gmail.com>
To: Michael Di Domenico <mdidomenico4@gmail.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: nic enumeration
Date: Wed, 7 Jul 2010 17:39:37 -0500	[thread overview]
Message-ID: <20100707223935.GD23117@gmail.com> (raw)
In-Reply-To: <AANLkTimvsaoOm_QEUnvlZf2EKuiMpOr9PdQt_Ga0Z97D@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Michael Di Domenico <mdidomenico4@gmail.com> 2010-07-07 18:25:
> I have an issue where I have an onboard NIC with effectively three
> ports, no other NIC ports/chips are in the system
> 
> Nic0: xx:xx:xx:00:00:02
> Nic1: xx:xx:xx:00:00:01
> IPMI: xx:xx:xx:00:00:03
> 
> When I boot RedHat Linux, Nic1 becomes Eth0 and Nic0 becomes Eth1.
> 
> I understand there is a disconnect between BIOS and linux on which
> device should get which Eth, as well as, what ensues when you have PCI
> cards along side onboard ports.
> 
> What I'm curious about is how/why Linux actually decides Nic1 should be Eth0?
> 
> My theory is it starts on the lowest MAC address and works up,
> depending partly on driver load order.
> 
> Given the above scenario, swapping the MAC addresses between Nic1 and
> Nic0 would clear this issue.
> 
> Can anyone confirm or deny this?  Or explain/point me to, how it actually works.

Look into udev.  It should maintain some rules that dictate that
mapping.  If not you can potentially write/alter some to make it do what
you want/expect.

On my systems the place to look is generally here:
/etc/udev/rules.d (user rules)
/lib/udev/rules.d (system rules)

There may be others.

Cheers,
Brian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-07-07 22:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 22:25 nic enumeration Michael Di Domenico
2010-07-07 22:39 ` Brian Kroth [this message]
2010-07-07 23:15 ` Steve Fink
2010-07-08  1:21 ` Matt Domsch
2010-07-08 20:36   ` Loke, Chetan
2010-07-08 20:47     ` Andrew Fong
2010-07-08 21:27       ` Kay Sievers
2010-07-08 22:07         ` Loke, Chetan
2010-07-08 21:24     ` Charlie Brady
2010-07-09  7:18     ` Florian Weimer
2010-07-09  7:57       ` Kay Sievers
2010-07-09  8:13         ` Florian Weimer
2010-07-09 16:27       ` Loke, Chetan
2010-07-09 17:10         ` Steve Fink
2010-07-09 18:23           ` Loke, Chetan
2010-07-09 21:26             ` Steve Fink
2010-07-12 16:56               ` Loke, Chetan
2010-07-12 18:27                 ` Steve Fink
2010-07-09 17:15         ` Matt Domsch
2010-07-09 18:55           ` Loke, Chetan

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=20100707223935.GD23117@gmail.com \
    --to=bpkroth@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mdidomenico4@gmail.com \
    /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.