netdev - Re: Network Device Naming mechanism and policy

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: <49CA927B.9080709@nortel.com>
Date:	Wed, 25 Mar 2009 14:22:19 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	David Miller <davem@...emloft.net>
CC:	Matt_Domsch@...l.com, netdev@...r.kernel.org,
	linux-hotplug@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Network Device Naming mechanism and policy

David Miller wrote:
> From: Matt Domsch <Matt_Domsch@...l.com>
> Date: Tue, 24 Mar 2009 10:46:17 -0500
> 
>> Problem: Users expect on-motherboard NICs to be named eth0..ethN.
>> This can be difficult to achieve.
> 
> I learned a long time ago that eth0 et al. have zero meaning.
> 
> If the system firmware folks gave us topology information with respect
> to these things, we could export something that tools such as
> NetworkManager, iproute2, etc. could use.

<snip>

> I guess it's easier to spew about MAC addresses and other
> irrelevant topics than try to solve this problem properly. :-)

What about things like USB network adapters where the topology is not 
fixed?  Presumably we would want to use some sort of unique identifier, 
and the MAC comes to mind.  Of course, then you run into the problem of 
how to deal with duplicate MACs.

Chris
--
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