You are not logged in.

#1 2006-05-09 23:59:21

jason
Member
From: /dev/null
Registered: 2003-01-13
Posts: 100

Interface names jumping around

On my T43p, I'm having problems keeping my interfaces from changing names.  I've put the following in my udev rules:

(~) jayne $ cat /etc/udev/rules.d/01-network.rules
SUBSYSTEM=="net", SYSFS{address}=="00:11:22:33:44:55", NAME="eth0"
SUBSYSTEM=="net", SYSFS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth1"

But it's not helping.  They flop around anyways.  It's an ipw2200 card as eth1 and tg3 as eth0.

Any helpful hints?

Offline

#2 2006-05-10 00:10:19

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: Interface names jumping around

To me it seems that other rules besides udev.rules don't work anymore, but I will check that out to be sure.

[edit: checked out ... I was wrong, udev works fine]


1000

Offline

#3 2006-05-10 00:27:41

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: Interface names jumping around

Using ethX as names has failed often in the past. Use non-standard names for the devices instead. Otherwise the rules are ok.

Offline

#4 2006-05-10 03:24:06

jason
Member
From: /dev/null
Registered: 2003-01-13
Posts: 100

Re: Interface names jumping around

What's my alternative to keep the interface names stable?

Offline

#5 2006-05-10 06:03:51

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: Interface names jumping around

Load the modules in the MODULES array, in the order you'd like to have them.

BTW, all that information is on the Udev wiki page.

Offline

#6 2006-05-11 21:49:39

uberGeek
Member
From: Near Chicago
Registered: 2004-01-07
Posts: 65
Website

Re: Interface names jumping around

Loading modules in a particular order does not help a lot when two, or more, interfaces use the same module.

What I've found works best, for me anyway, is dtw's suggestion from here:
http://bbs.archlinux.org/viewtopic.php? … ght=mactab
Search for mactab on that page.  It requires an edit to /etc/rc.d/network, so it's not ideal, but until the ideal works (udev with ethX names) I'm going with it.  It has been working for me on 4 or 5 machines (all with 2 to 3 interfaces) for a month now.

In my opinion, using a name other than ethX, in a udev rule, is not a fix, it's a workaround to a bug.


carb $ now; uname -a; uptime
Sun 03Jul11 14:54:25 CDT -0500
Linux carb 2.6.17-ARCH #1 SMP PREEMPT Fri Jul 7 09:15:53 CEST 2006 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
14:54:25 up 1463 days,  9:24,  1 user,  load average: 1.00, 1.00, 1.00

Offline

Board footer

Powered by FluxBB