You are not logged in.

#1 2006-04-05 09:09:56

cogo
Member
From: no_NO
Registered: 2006-01-19
Posts: 56
Website

NIC changed from eth0 to eth2

Just did a pacman -Syu to get the kde updates and such ... and when I rebooted, my NIC was changed from eth0 to eth2 ... I saw that ipw2200 was among the updates... could that cause this?

Offline

#2 2006-04-05 11:06:48

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

Re: NIC changed from eth0 to eth2

Offline

#3 2006-04-05 12:05:54

cogo
Member
From: no_NO
Registered: 2006-01-19
Posts: 56
Website

Re: NIC changed from eth0 to eth2

Thanks. I will try to make a udev rules file. I'll see what happens next reboot. smile

Offline

#4 2006-04-09 10:06:42

cogo
Member
From: no_NO
Registered: 2006-01-19
Posts: 56
Website

Re: NIC changed from eth0 to eth2

Well ... now I think that my NIC gets eth0, and my wlan NIC gets eth1 every time, but sometimes none of them gets set up at all.

I boot, and when I do en ifconfig, the only thing that shows up is 'lo'. If I try 'ifconfig eth0 up' and 'dhcpcd eth0', eth0 does not get set up correctly. I then try a reboot, and usually the NICs work after the reboot.

I added an 10-network.rules in the /etc/udev/rules.d/ folder which contains the following lines:
<code>SUBSYSTEM=="net", SYSFS{address}=="00:0b:5d:77:b3:aa", NAME="eth0"
SUBSYSTEM=="net", SYSFS{address}=="00:0e:35:da:97:36", NAME="eth1"</code>

In /etc/rc.conf I have:

<code>lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 !eth1)</code>

Anyone who can help me out here? smile

Offline

#5 2006-04-09 13:08:13

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

Re: NIC changed from eth0 to eth2

In some cases, reassigning the standard names (ethX) was unsuccessful. Instead, try names like "lan0", "wlan0", "foo", "bar" or "noodle" for your interfaces. This always worked so far.

Offline

#6 2006-04-09 14:24:12

Sander
Member
Registered: 2006-02-26
Posts: 138

Re: NIC changed from eth0 to eth2

yep, naming them eth0, eth1 isn't a good idea (I found out the hard way). I named them lan0 and lan1 after that, but some crappy program required me to have an eth0 to activate it, so I had to resort to listing the modules manually in rc.conf to get the order fixed.


You like cheese? You like peas? You'll love cheezy peas!

Offline

Board footer

Powered by FluxBB