New network naming schema in systemd 197

HalosGhost · 2013-04-02 02:22:04

silentsnake wrote:

Whats wrong if I've upgraded systemd but still stuck with the classic ethX naming?
Read the mailing list, sorry didn't saw the posting the first time.

Delete the udev rule. Might be helpful to re-read the mailing list post.

All the best,

-HG

microcz · 2013-04-02 08:21:00

Hi everybody, I put new arch on my girlfriend's HP5103, but strange problem with Wifi interface name has appeared.

The name of same wlan interface constantly changes from wlan0 to wlp1s0 and vice versa. I am pretty confused with it because netcfg profiles, I've configured, do not work. I have to change netcfg profiles each time i reboot.

Example:
1. reboot: wlan0
2. reboot: wlp1s0
3. reboot: wlan0
4. reboot: wlp1s0
etc.....

Is there a way to have always same name of interface?

jasonwryan · 2013-04-02 08:28:02

Merging with the stickied thread...

renegat · 2013-04-30 16:35:03

Did anybody notice that there is a problem with WPA supplicant daemon (interface-specific version)?

I was trying to get wireless to work by using systemd, wpa_supplicant and dhcpcd and followed the way given here in the wiki but using the new network names.

So I changed every 'wlan0' against 'wlp2s0' but this didn't not work with that new network naming schema in systemd because the link created by

# systemctl enable wpa_supplicant@wlp2s0.service

in /etc/systemd/system/multi-user.target.wants/ is always named wpa_supplicant@wlan0.service!

But there is no wlan0 anymore! You have to rename the link by yourself

# mv /etc/systemd/system/multi-user.target.wants/wpa_supplicant\@wlan0.service /etc/systemd/system/multi-user.target.wants/wpa_supplicant\@wlp2s0.service

to make it work.

65kid · 2013-04-30 16:44:55

renegat wrote:

Did anybody notice that there is a problem with WPA supplicant daemon (interface-specific version)?
I was trying to get wireless to work by using systemd, wpa_supplicant and dhcpcd and followed the way given here in the wiki but using the new network names.
So I changed every 'wlan0' against 'wlp2s0' but this didn't not work with that new network naming schema in systemd because the link created by
# systemctl enable wpa_supplicant@wlp2s0.service
in /etc/systemd/system/multi-user.target.wants/ is always named wpa_supplicant@wlan0.service!
But there is no wlan0 anymore! You have to rename the link by yourself
# mv /etc/systemd/system/multi-user.target.wants/wpa_supplicant\@wlan0.service /etc/systemd/system/multi-user.target.wants/wpa_supplicant\@wlp2s0.service
to make it work.

upstream bug: http://hostap.epitest.fi/bugz/show_bug.cgi?id=477

ddjolley · 2013-04-30 23:17:17

I am trying to get Wifi working using netctl.

I have removed the netcfg package and installed the netctl and wpa_actiond packages.

Here is where I stand:

[root@nb505 doug]# lspci | grep -i net
07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
[root@nb505 doug]# lsmod | grep -i rtl
rtl8192ce              46876  0 
rtlwifi                56313  1 rtl8192ce
rtl8192c_common        32575  1 rtl8192ce
mac80211              401303  3 rtlwifi,rtl8192c_common,rtl8192ce
cfg80211              368786  2 mac80211,rtlwifi
usbcore               148267  7 uhci_hcd,uvcvideo,rtlwifi,usb_storage,ehci_hcd,ehci_pci,usbhid
[root@nb505 doug]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether b8:70:f4:d7:8e:15 brd ff:ff:ff:ff:ff:ff
3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
    link/ether 74:de:2b:61:6c:e7 brd ff:ff:ff:ff:ff:ff
[root@nb505 doug]#

journalctl -xn says that 'wlan0' does not exist. My gut feeling is that that is correct in that the interface is missing. I'm not sure that I can expect it to be named wlan0. Anyway, I'm sort of lost. One can't get to first base until the interface is created. I would expect to see the interface (whatever it is named) in the output of "ip link". As you can see, I don't. Can anyone please guide me towards getting back on track? Thanks for any input.

... doug

Last edited by ddjolley (2013-04-30 23:36:35)

HalosGhost · 2013-04-30 23:22:01

ddjolley wrote:

Can anyone please guide me towards getting back on track? Thanks for any input.

There was a systemd update a while back (197, I believe) that created predictable naming schemes for network interfaces. Your wireless interface is named "wlp7s0" and your wired interface is "enp9s0."

Please search in the future, this has been covered before.

[Edit]: Removed redundant link after the merge. Thank you jasonwryan!

All the best,

-HG

Last edited by HalosGhost (2013-05-01 00:36:38)

jasonwryan · 2013-04-30 23:23:24

Merging...

ddjolley · 2013-05-01 00:34:29

Thanks. Your input is both helpful and appreciated. I read about predictable naming schemes. However, with all the changes it's confusing as to what applies to what and the error message did specifically say that the wlan0 interface was missing. Sorry to be so dense. Thanks.

... doug

jackbenny · 2013-07-19 13:29:12

microcz wrote:

Hi everybody, I put new arch on my girlfriend's HP5103, but strange problem with Wifi interface name has appeared.
The name of same wlan interface constantly changes from wlan0 to wlp1s0 and vice versa. I am pretty confused with it because netcfg profiles, I've configured, do not work. I have to change netcfg profiles each time i reboot.
Example:
1. reboot: wlan0
2. reboot: wlp1s0
3. reboot: wlan0
4. reboot: wlp1s0
etc.....
Is there a way to have always same name of interface?

I have the exact same problem. Although my interface names keeps to the old naming scheme ethX/wlanX about 80% of the boots. The other 20% of the boots I get the new naming scheme wlpsXsX/enpXsX. I've been banging my head against this for the past three days.
I've checked my configs over and over.

1. I have no /etc/udev/rules.d/80-net-name-slot.rules. It does exist in /usr/lib/udev/rules.d just as it should thouh.
2. I have no net.ifnames=0 in my kernel parameters. I have tried setting it to net.ifnames=1 though, but it didn't make a diffrence.
3. I have tested with "udevadm test-builtin net_id /sys/class/net/eth0 (and wlan0)" and I should be able to get the "new" names, since it respond with ID_NET_NAME_PATH=enp3s0 and ID_NET_NAME_PATH=wlp2s0.
4. I have no custom-made naming sheme rules in place.

The installation is rather fresh and the ISO I used for installation is about a month old so it should default to the new naming scheme. I have 3 other computers running Arch which has all been installed around the same time with same ISO and updates, and they are all using the new predictable interface names only. No switching back and forth from ethX to enpXsX on them.

Anyone got any ideas to where I should start looking for a solution to this?

castro · 2013-09-18 09:59:09

This worked for me.

file: /etc/udev/rules.d/10-network.rules

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:a0:24:a8:50:a5", NAME="wan_if" 
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:0f:ea:32:9d:01", NAME="lan_if"

More info can be found here.
https://wiki.archlinux.org/index.php/Ne … vice_names

karol · 2013-09-18 11:14:41

Hi, castro and welcome to arch Linux forums :-)
Usually there's no need to bump threads with info that's in the wiki. Everyone should be able to find it on their own.

fukawi2 · 2013-09-18 12:38:45

I think this thread has served it's purpose. Enough water has passed under the bridge to warrant new threads for any issues coming up now with the new naming scheme.

Closing.

Arch Linux

#151 2013-04-02 02:22:04

Re: New network naming schema in systemd 197

#152 2013-04-02 08:21:00

Re: New network naming schema in systemd 197

#153 2013-04-02 08:28:02

Re: New network naming schema in systemd 197

#154 2013-04-30 16:35:03

Re: New network naming schema in systemd 197

#155 2013-04-30 16:44:55

Re: New network naming schema in systemd 197

#156 2013-04-30 23:17:17

Re: New network naming schema in systemd 197

#157 2013-04-30 23:22:01

Re: New network naming schema in systemd 197

#158 2013-04-30 23:23:24

Re: New network naming schema in systemd 197

#159 2013-05-01 00:34:29

Re: New network naming schema in systemd 197

#160 2013-07-19 13:29:12

Re: New network naming schema in systemd 197

#161 2013-09-18 09:59:09

Re: New network naming schema in systemd 197

#162 2013-09-18 11:14:41

Re: New network naming schema in systemd 197

#163 2013-09-18 12:38:45

Re: New network naming schema in systemd 197

Board footer