Bug 378758

Summary: yast2 network module creates slightly wrong udev rule
Product: [openSUSE] openSUSE 11.0 Reporter: Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: mt
Version: Alpha 3plus   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User ZhJd0F0L3x 2008-04-10 14:07:05 UTC
I installed STABLE yesterday, today i configured the network with YaST.
I was very pleased to find an option to configure the device name, since i usually did this by editing the udev-rules by hand :-)

Unfortunately, it did not work correctly for my wireless interface:
[   14.096716] udev: renamed network interface wmaster0 to air
but it shoudl have renamed the wlan0 interface.

wlan0 was renamed "wlan0_rename" for some reason.

I fixed the udev rule like that:
--- /tmp/70-persistent-net.rules        2008-04-10 15:56:45.000000000 +0200
+++ 70-persistent-net.rules     2008-04-10 15:57:31.000000000 +0200
@@ -10,5 +10,5 @@
 # You can modify it,as long as you keep each rule on a single line.
 # PCI device 0x8086:0x4229 (iwl4965)
 # PCI device 0x8086:0x1049 (e1000e)
-SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1d:e0:9b:ee:e3", NAME="air"
+SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1d:e0:9b:ee:e3", ATTR{type}=="1", NAME="air"
 SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:24:f0:b9:68", NAME="cable"

and now it is working fine.
I have no knowledge about udev rules at all, so i'll take Christian and Kay into cc :-)
Comment 1 Michal Zugec 2008-04-10 14:16:36 UTC
Just to know, some words about that feature are here:
http://en.opensuse.org/YaST/Network/11.0-device_name

Hm, I didn't know that ATTR{type} is so important
Comment 2 Michal Zugec 2008-04-24 12:33:12 UTC
marked as duplicate of bug #383320 (I know, this one was first but second one has a better explained description)

*** This bug has been marked as a duplicate of bug 383320 ***