Messages in this thread | | | Subject | Re: NICs trading places ? | From | Sean Neakums <> | Date | Fri, 28 Mar 2003 23:42:51 +0000 |
| |
commence Dax Kelson quotation:
> On Fri, 28 Mar 2003, Dave Jones wrote: > >> I just upgraded a box with 2 NICs in it to 2.5.66, and found >> that what was eth0 in 2.4 is now eth1, and vice versa. >> Is this phenomenon intentional ? documented ? >> What caused it to do this ? > > I've seen the same thing for 5+ years. Multiple things can > trigger it, eg: > > Always having your NIC drivers compiled in, and then moving between > different kernel versions. > > Going from modular NIC drivers to compiled in drivers can bite you. > > Isn't life fun.
Something I have been meaning to write as soon as I get bitten by this myself is a script that uses the "ip link set X name Y" command (possibly in conjuction with a MAC-to-name map, or else just a simple sort) to name the interfaces consistently.
-- Sean Neakums - <sneakums@zork.net> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |