From: Jonathan Wood <jonwood@sp...> - 2002-08-23 20:02:49
Creation of netdevices seems to be ordered alphabetically by the name
of the UML network transport. This can lead to some unexpected
assignments of transports to interfaces. For example, if I start UML
# linux ubd0=root_fs eth0=mcast eth1=daemon
it turns out that eth0 gets the daemon transport and eth1 gets the mcast
transport (contrary to what the boot output says...). This can be
ethereal on the host, and can be fixed simply by reordering the
# linux ubd0=root_fs eth0=daemon eth1=mcast
(Of course you will need to update your interface initialization scripts
the UML instance as well).
This first showed up in 2_4_18_38, I am now using 2_4_19_1. I suspect
that it is a side effect of the latest change to net_kern.c, which
transport registration is done...
So the question is: is this a bug, or just something that should be
From: David Coulson <david@da...> - 2002-08-23 20:31:54
Jonathan Wood wrote:
> So the question is: is this a bug, or just something that should be
It's the kernel - It assigns eth devices in the order you register them,
so eth0 and eth1 on the command line means nothing. However, I've found
with UML that it'll always assign them in the same order, so eth0 will
always be eth0, even if you do 'eth7='
You can use 'nameif' to set interface names based on MAC address, which
may be more useful.
David Coulson http://davidcoulson.net/
Get latest updates about Open Source Projects, Conferences and News.