| View previous topic :: View next topic |
| Author |
Message |
alexbuell
Guru
Joined: 18 Jul 2002
Posts: 498
Location: "Hemp"shire, UK
|
 Posted: Wed Sep 08, 2010 3:59 pm Post subject: [SOLVED] udev problem with renaming network interfaces |
 |
|
I recently swapped my rubbish Broadcom b4309 mini-PCI network card with an Atheros wireless-N wireless mini-pci, and made the appropriate changes in /etc/udev/rules.d/70-net-persistant.rules to ensure that the interface remained wlan0.
Today I swapped out the Atheros card with an Intel 2915ABG card, changed the rules to ensure it kept wlan0 as its interface name. However, on reboot, udev refused to use the wlan0 name and added another rule to keep its interface to eth1.
I deleted that rule and rebooted again. It still added it back in, still eth1.
Is there anything I can do to FORCE udev to keep it as wlan0?
Many thanks!
_________________
Cheers,
Alex.
Linux - the best text adventure game ever.
Last edited by alexbuell on Fri Sep 10, 2010 7:36 am; edited 1 time in total |
|
| Back to top |
|
 |
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6222
Location: Dallas area
|
| Posted: Wed Sep 08, 2010 4:59 pm Post subject: |
|
|
What does it do if you delete the 70-net-persistant.rules file (or move it out of the directory) and then reboot?
_________________
UM780, 6.12 zen kernel, gcc 13, openrc, wayland |
|
| Back to top |
|
|
alexbuell
Guru
Joined: 18 Jul 2002
Posts: 498
Location: "Hemp"shire, UK
|
| Posted: Wed Sep 08, 2010 6:01 pm Post subject: |
|
|
| Anon-E-moose wrote: | | What does it do if you delete the 70-net-persistant.rules file (or move it out of the directory) and then reboot? |
Then I get:
| Code: |
# PCI device 0x14e4:0x4401 (b44)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0d:56:38:97:3
3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x4223 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:12:f0:9d:f6:8
c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
|
Wireless gets eth0 and wired gets eth1. Strange, isn't it?
I've put back the original rules set now, as there are other interfaces that doesn't change. Any other ideas? This is strange, I really need for it to go back to wlan0 and not become eth1 nor eth0!
_________________
Cheers,
Alex.
Linux - the best text adventure game ever. |
|
| Back to top |
|
|
alexbuell
Guru
Joined: 18 Jul 2002
Posts: 498
Location: "Hemp"shire, UK
|
| Posted: Thu Sep 09, 2010 12:15 pm Post subject: |
|
|
I'm still no nearer the answer 
_________________
Cheers,
Alex.
Linux - the best text adventure game ever. |
|
| Back to top |
|
|
alexbuell
Guru
Joined: 18 Jul 2002
Posts: 498
Location: "Hemp"shire, UK
|
| Posted: Fri Sep 10, 2010 7:38 am Post subject: |
|
|
I finally solved it.
I had this:
| Code: |
# PCI device 0x8086:0x4223 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:12:f0:9d:f6:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
|
This did not work as it already was named eth1 so the rule did not match it. Changing this to:
| Code: |
# PCI device 0x8086:0x4223 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:12:f0:9d:f6:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
|
This solved it for me. I've left this as a note so others can refer to this in the future.
_________________
Cheers,
Alex.
Linux - the best text adventure game ever. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
