netdev - network interface *name* alias support?

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

Message-Id: <1211410078.27149.70.camel@perihelion>
Date:	Wed, 21 May 2008 18:47:58 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	netdev <netdev@...r.kernel.org>
Subject: network interface *name* alias support?

Hi,

I would like to add support for network interface name aliases to the
kernel. For example, rather than simply "eth0", one might have:

eth0 -> eth_slot_0_0

And use either name for device configuration, etc. This should be pretty
easy, but I would like some comments - in particular, has this been done
already and I'm missing something?

Why is this useful? Say, for example that your a manufacturer building
machines using the latest DMI extension to SMBIOS that allows you to
specify what the physical ordering of interfaces is. Then, a
distribution might choose to configure based on the physical slot
ordering specified by the vendor - allowing for "rip and replace".

Jon.

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