From: Dan Williams <dcbw@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Specifying netdev name on kernel boot?
Date: Thu, 15 Aug 2013 13:09:03 -0500 [thread overview]
Message-ID: <1376590143.2180.11.camel@dcbw.foobar.com> (raw)
In-Reply-To: <520CF8BB.2080702@candelatech.com>
On Thu, 2013-08-15 at 08:50 -0700, Ben Greear wrote:
> It seems they finally broke udev in Fedora 19...it can no longer
> rename ethX to ethY, for whatever reason.
It's intentional AFAIK, it won't rename devices into the kernel
namespace (eth, wlan, usb, wwan) because it's inherently race-prone and
there's no way to know that the kernel didn't just detect a new eth2
while you're about to rename your eth0 to eth2. There actually have
been a lot of problems with that in past, because bus enumeration order
is not guaranteed.
I'm pretty sure you drop a rule in /etc/udev/rules.d to what you want:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Or if you install biosdevname, you'll get the nice BIOS names for the
interfaces which is usually something like "slot1nic0" or "builtin0" or
something like that.
(and yeah, one of my devices is "enp0s29f7u4" which is just f-king ugly.
*I* know what that means and why udev is doing it, but I also sympathize
with those who don't...)
Dan
> Is there a way to specify the naming on the kernel command line?
>
> I found something in google that made me think this might work:
>
> ifname=eth0:00:30:48:fc:17:a2 ifname=eth1:00:30:48:fc:17:a3 ifname=eth2:00:e0:ed:1c:ec:e4 ifname=eth3:00:e0:ed:1c:ec:e5
>
> but it doesn't seem to have any affect.
>
> I'm using ixgbe and e1000e drivers, loaded as modules, in case that matters.
>
> Thanks,
> Ben
>
next prev parent reply other threads:[~2013-08-15 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 15:50 Specifying netdev name on kernel boot? Ben Greear
2013-08-15 18:09 ` Dan Williams [this message]
2013-08-15 18:26 ` Ben Greear
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=1376590143.2180.11.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=greearb@candelatech.com \
--cc=netdev@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.