linux-kernel - Re: Device naming randomness (udev?)

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] [day] [month] [year] [list]

Message-ID: <45765DBB.7010703@mbligh.org>
Date:	Tue, 05 Dec 2006 22:05:47 -0800
From:	"Martin J. Bligh" <mbligh@...igh.org>
To:	Greg KH <gregkh@...e.de>
Cc:	Bj?rn Steinbrink <B.Steinbrink@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	tony@...eyournoodle.com
Subject: Re: Device naming randomness (udev?)

Greg KH wrote:
> On Mon, Dec 04, 2006 at 12:12:06AM +0100, Bj?rn Steinbrink wrote:
>> On 2006.12.03 14:39:44 -0800, Martin J. Bligh wrote:
>>> This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.
>>>
>>> On 2.6.14, my e1000 interface appears as eth0.
>>> On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.
>>>
>>> In both cases, there are no other ethX interfaces listed in
>>> "ifconfig -a". There are no modules involved, just a static
>>> kernel build.
>>>
>>> Is this a bug in udev, or the kernel? I'm presuming udev,
>>> but seems odd it changes over a kernel release boundary.
>>> Any ideas on how I get rid of it? Makes automatic switching
>>> between kernel versions a royal pain in the ass.
>> Just a wild guess here... Debian's (and I guess Ubuntu's) udev rules
>> contain a generator for persistent interface name rules. Maybe these
>> start working with 2.6.15 and thus the switch (ie. the kernel would call
>> it eth0, but udev renames it to eth1).
>> The generated rules are written to
>> /etc/udev/rules.d/z25_persistent-net.rules on Debian, not sure if its
>> the same for Ubuntu. Editing/removing the rules should fix your problem.
> 
> Yes, I'd place odds on this one.

Huh. Somehow there was this entry in /etc/iftab:

eth0 mac 00:0d:61:44:90:12 arp 1

But that's not my mac address. Damned if I know how that got there, but
if the persistent rules only work on later kernels, that'd explain it.
And indeed ... removing that entry makes it work more normally.

Thanks for the pointers - most helpful.

M.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/