netdev - Re: Provide ability to change default netdev name?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1376696468.11042.74.camel@deadeye.wl.decadent.org.uk>
Date:	Sat, 17 Aug 2013 01:41:08 +0200
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Ben Greear <greearb@...delatech.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: Provide ability to change default netdev name?

On Fri, 2013-08-16 at 15:14 -0700, Ben Greear wrote:
> The latest udev in Fedora 19 (and perhaps elsewhere) will no longer
> implement rules that rename an interface from ethX to ethY.  Nor
> wlanX or other 'kernel namespaces'.  The Fedora udev developers do not seem
> interested in changing this back to the old behaviour, evidently they
> had a hard time implementing it properly.

There is an inherent problem that a new device can appear at any time
under the exact name udev is trying to rename to.  I expect it is
possible to do this properly but may be quite difficult to eliminate the
possibility of deadlock.

Still, if udev actively refuses to use the 'kernel namespaces' (rather
than just being configured not to), that would be a bug.

> This effectively makes it impossible to have network device names of ethX
> consistent across reboots in systems with multiple NICs and/or drivers.
> 
> One way to work around this would be allow the kernel to use a different
> default netdev name (for instance, keth%d).  I'm thinking this would be
> configured as a kernel command line argument.  Then, a small change to udev/systemd to
> make the 'kernel namespaces' configurable by letting it understand this new kernel
> command line argument should resolve the problem.
> 
> Does this sound like something that could be accepted upstream?

This sounds completely ridiculous.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html