linux-kernel - Re: drivers/net/usb/asix: strange numeration of eth interfaces

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: <20111219.141128.1563372305361818137.davem@davemloft.net>
Date:	Mon, 19 Dec 2011 14:11:28 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	igor@...rkin.ru
Cc:	linux-kernel@...r.kernel.org, allan@...x.com.tw,
	grundler@...omium.org
Subject: Re: drivers/net/usb/asix: strange numeration of eth interfaces

What you're seeing isn't strange, it depends upon what ethernet devices were
visible when you installed your machine.

'udev' in userspace remembers the mappings from ethernet addresses to
device names, and renames devices as the system comes up to what it
first saw them as, based upon the MAC address.

So one possibility is that there were 2 other ethernet or wireless devices
in your system at install time, so the one that the ASIX device got was
'eth2'.

Therefore that is the device name it will have until you tell 'udev' to
do otherwise.
--
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/