Re: Controlling eth0,eth1,... assignment order?
- To: firstname.lastname@example.org
- Subject: Re: Controlling eth0,eth1,... assignment order?
- From: Thomas Jollans <email@example.com>
- Date: Mon, 02 Jan 2006 12:58:39 +0100
- Message-id: <[🔎] 43B9156F.firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
Stefhen Hovland wrote:
>i think ifrename will do what you are asking, you can specify that
>eth0 always be bound to x, and eth1 always bound to y, etc..
>On 12/29/05, Svante Signell <email@example.com> wrote:
>>With the new way of device creation and module loading (udev, discover
>>etc) my ethernet modules (3c59x,8139too) are loaded in different order
>>with kernels 2.6.12 and 2.6.14. For 2.6.14 3c59x is loaded first
>>corresponding to eth0 and then 8139too corresponding to eth1. With
>>kernel 2.6.12 they are loaded in reverse order, giving the wrong names
>>on my interfaces, and the interfaces defined in /etc/network/interfaces
>>becomes wrong. How to bind modules to eth interface numbers? Any hints
>>on which of the /etc/modules, /etc/modules.conf etc should be used, and
>>which are obsolete?
udev should work here. you can set it up. You can set up devices to have
certain names (e.g. you camera as /dev/camera) with it , and I heard
this works with network interfaces too. google is your friend if you
want more informtion, I hope.