On Wed, 22 Sep 2010 23:07:53 +0100 Tim Small <tim@xxxxxxxxxxxxxxxx> wrote: > Narendra K wrote: > > Hello, > > > > Here is another approach to address the issue of "eth0 does not always > > map to the Integrated NIC Port 1 as denoted on server chassis label". > > For more details please refer to the thread - > > http://marc.info/?l=linux-netdev&m=128163454631618&w=3. > > > > > Hi, > > Out of interest, that link says that doing it in usespace was rejected, > but doesn't give any references... I'd be interested to know why this > wasn't viable - since this seemed like the best fit at first glance - > most people will never use this, so no need to grow their kernel size > and complexity? > This proposal was to ad changes into every application that knows about network names (iproute, iptables, snmp, quagga, openswan, ...) to do aliasing at the application layer. I rejected it as an unmanageable since it would require changes to so many packages (many of which are more BSD focused). Also doing aliasing would lead to security and other issues. For example, if you write a iptables rule based on the "Embedded NIC 1" rule would it work and know when the packet name lookup returned eth0, or what about device names in the Quagga RIB, ... -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
