From: P@draigBrady.com
To: Alex Upton <AUpton@island.com>
Cc: netdev@oss.sgi.com
Subject: Re: 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic
Date: Fri, 11 Mar 2005 14:27:08 +0000 [thread overview]
Message-ID: <4231AABC.8040101@draigBrady.com> (raw)
In-Reply-To: <13A26154A563124B876A26F0EF0CE1ED032C9299@HFCCINFEXCH501.AMERICAS.CORP.LOCAL>
Alex Upton wrote:
> Hello All,
>
> For about 3.5 days now I've been trying to swap eth0 and eth1 devices
> through use of the netdev kernel boot switch.
>
> The scenario:
>
> We have a system with onboard NICS and a PCI Intel e1000 Fiber NIC
> installed. This particular system by default forces the NIC inside the
> PCI slot to always default to eth0. We want to have ultimate control as
> to which NIC is deemed worthy enough to become eth0. We are using an
> entirely monolithic kernel via a PXE driven build and prefer not to
> support use of modules.
>
> If anyone has any suggestions or insight on how to work with netdev and
> the e1000 properly it would be greatly appreciated!
I've found using a higher level script with heuristics
is the only way to order nics generically as I want. for e.g.
if ethtool eth0 | grep -q "Port: FIBRE"; then
ip link set dev eth0 name not_eth0
ip link set dev eth1 name eth0
fi
you get the idea...
Pádraig.
next prev parent reply other threads:[~2005-03-11 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 14:00 2.6.10 - "netdev=" kernel boot commands and the Intel e1000 nic Alex Upton
2005-03-11 14:12 ` jamal
2005-03-11 14:27 ` P [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 18:23 Jean Tourrilhes
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=4231AABC.8040101@draigBrady.com \
--to=p@draigbrady.com \
--cc=AUpton@island.com \
--cc=netdev@oss.sgi.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.