New network naming schema in systemd 197

jasonwryan · 2013-02-18 19:38:56

Merging with said stickied...

WonderWoofy · 2013-02-18 19:45:52

jtag1458, welcome to the Arch Linux forums! You should use the beginners guide rather than the lifehacker guide. Guides found across the internet can have a horrible result due to their becoming outdated rather quickly, as is the case here. Apparently it even tells you to use rc.d, which was part of SysV init that is no longer used around here.

It is probably advisable to start again and follow the beginners guide, so you get an understanding of what you are doing and why, and getting correct information along the way.

tsouzar · 2013-02-24 18:32:31

Hello.

Today a problem appeared here: netcfg isn't starting the wireless interface anymore on boot.
I runned

systemctl status netcfg

and get this:

netcfg.service - Netcfg multi-profile daemon
Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
Active: failed (Result: exit-code) since Dom 2013-02-24 14:31:22 BRT; 3min ago
Process: 289 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/netcfg.service
└─351 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa.wlan0/wpa.conf
Fev 24 14:31:16 LinuxPC netcfg-daemon[289]: :: wlan0 up wpa_supplicant did not start, possible configuration error
Fev 24 14:31:16 LinuxPC netcfg-daemon[289]: [fail]
Fev 24 14:31:22 LinuxPC netcfg-daemon[289]: :: eth0 up No connection
Fev 24 14:31:22 LinuxPC netcfg-daemon[289]: [fail]
Fev 24 14:31:22 LinuxPC systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
Fev 24 14:31:22 LinuxPC systemd[1]: Failed to start Netcfg multi-profile daemon.
Fev 24 14:31:22 LinuxPC systemd[1]: Unit netcfg.service entered failed state

I have changed nothing in wlan0 profile, much less in wpa_supplicant or Netcfg settings, this problem came unexpectedly.
If I run

netcfg up wlan0

, the interface establishes connection normally.
I have other Netcfg profile here called eth0, an ethernet home network connection, and it works normally on boot.

If helps...:

Netcfg settings (/etc/conf.d/netcfg):

NETWORKS=(wlan0 eth0)
# I use net-auto-wired and ifplugd
WIRED_INTERFACE="eth0"
# This is off because I don't need net-auto-wireless. I tested using it and this not solves the problem.
# WIRELESS_INTERFACE="wlan0"

wlan0 profile (/etc/network.d/wlan0):

CONNECTION='wireless'
DESCRIPTION='Internet'
INTERFACE='wlan0'
SECURITY='none'
ESSID='iLG10'
IP='dhcp'

I don't know whether there is some relation with the problem, but before the problem appears I was testing other desktop environments, including Enlightenment 17, which has its own network manager, econnman (I disabled netcfg during the test). Some little slowness in system and browsing arose after the tests but already was eased. I currently use LXDE and have tested E17 and Razor-Qt, also tested login managers (LightDM and Slim - I use LXDM).

Ah, a question a little related to this topic: my wireless connection is open and has no encryption, why Netcfg needs wpa_supplicant at this case?

Thanks the attention and bye.

Last edited by tsouzar (2013-02-24 20:47:15)

jim_bo · 2013-02-24 22:19:44

Hi

The last systemd update (systemd 197) change the historical network name like eth0 et wlan0 by something like wlp13s0 or enp14s0

check the new name with ifconfig

In etc/network.d/wlan0 file the INTERFACE refer to 'wlan0' ; maybe you can try the new network name here

on my laptop the only way to get network at startup was to disable and delete netfcg and then install and enable network-manager

Last edited by jim_bo (2013-02-24 22:20:32)

jasonwryan · 2013-02-24 22:53:23

Merging with the stickied thread...

tsouzar · 2013-02-25 01:28:09

Here, ifconfig and ip link shows the old names (eth0, wlan0...).
My systemd version is 197-4.

How can I use and know the new names?

ewaller · 2013-02-25 02:15:53

tsouzar wrote:

Here, ifconfig and ip link shows the old names (eth0, wlan0...).
My systemd version is 197-4.
How can I use and know the new names?

What you are looking for is in the wiki, but it is hard to find (seriously)

https://wiki.archlinux.org/index.php/Ne … vice_names

Edit: Hint, Just remove the symlink

Last edited by ewaller (2013-02-25 02:17:20)

tsouzar · 2013-02-25 13:33:02

ewaller wrote:

tsouzar wrote:
Here, ifconfig and ip link shows the old names (eth0, wlan0...).
My systemd version is 197-4.
How can I use and know the new names?
What you are looking for is in the wiki, but it is hard to find (seriously)
https://wiki.archlinux.org/index.php/Ne … vice_names
Edit: Hint, Just remove the symlink

There was none symlink, but a normal text file. I removed it and the new names came up
From wlan0 to wlp2s2
From eth0 to enp1s0
This was a sudden change.

Thanks! All working fine now...

Last edited by tsouzar (2013-02-25 13:35:41)

iamgabo · 2013-03-18 19:33:40

Hi folks! I've recently installed Arch in my new box. I have a wireless TP-LINK card, which uses the ath9k_htc module.
The problem that i've got is that it isn't recognized as default wlan0 by iwconfig. Instead of that:

wlp0s18f2u1  IEEE 802.11bgn  ESSID:"*"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: FF:FF:FF:FF:FF:FF   
          Bit Rate=24 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=30/70  Signal level=-80 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:7039   Missed beacon:0

lo        no wireless extensions.

Linux localhost 3.8.3-2-ck #1 SMP PREEMPT Sun Mar 17 16:36:28 EDT 2013 x86_64 GNU/Linux

I've used this exact same card with my other box, which has Archlinux too. Is this a Firmware issue?
Anyway, the card works, but it's a harsh to write that instead of 'wlan0' to use for security purposes (ettercap, aircrack, and so long).

Thanks in advance!

jasonwryan · 2013-03-18 19:35:02

Merging with the stickied thread in Networking...

WonderWoofy · 2013-03-18 22:28:06

@iamgabo, you need to mask 80-net-name-slot.rules.

Nik20 · 2013-03-21 00:24:56

I have just installed arch linux. When I boot with cd and chroot into the root, everything is fine and ifconfig prints eth0 and wlan0 and I can connect to internet using the wifi-menu command. But when I boot normally from hard disk, when I type wifi-menu I get this error:

No such interface:wlan0

and ifconfig lists only a device named lo, and ifconfig -a prints:

enp19s0: ...
lo:...
wlp18s0:...

I have installed arch before, but my interfaces were not renamed to this names. Why interfaces are renamed to this names at all? Is there a way to change them to eth0 and wlan0? And why wifi-menu prints this error?

Thanks

jasonwryan · 2013-03-21 00:31:30

Read the sticky above this thread...

Merging.

mhlbrothers · 2013-03-22 04:24:06

So just installed Archlinux for the first time on my system. Ran dhcpcd and here's what I get:

dhcpcd[4339]: version 5.6.7 starting
dhcpcd[4339]: enp0s7: sending IPv6 Router Solicitation
dhcpcd[4339]: enp0s7: broadcasting for a lease
dhcpcd[4339]: enp0s7: offered 192.168.0.203 from 192.168.0.1
dhcpcd[4339]: enp0s7: acknowledged 192.168.0.203 from 192.168.0.1
dhcpcd[4339]: enp0s7: checking for 192.168.0.203
dhcpcd[4339]: enp0s7: sending IPv6 Router Solicitation
dhcpcd[4339]: enp0s7: leased 192.168.0.203 for 86400 seconds
dhcpcd[4339]: forked to background, child pid 4365

So what is enp0s7? I'm guessing its eth0 in some other laguage. Did I do something wrong when I was installing? Is it supposed to be like this?

Any help would be great and thank you.

bohoomil · 2013-03-22 04:27:18

https://wiki.archlinux.org/index.php/Co … Interfaces

cookies · 2013-03-22 04:35:27

That's no strange language, it's the new device naming scheme introduced with systemd 197. See https://mailman.archlinux.org/pipermail … 24231.html for more info.

Edit: damn, too late... I should start bookmarking that stuff

Last edited by cookies (2013-03-22 04:36:54)

mhlbrothers · 2013-03-22 04:51:31

Well that is just confusing thanks for the help.

jasonwryan · 2013-03-22 07:14:11

Merging with the stickied thread...

demas · 2013-03-30 05:14:56

I am trying to install Arch Linux as guest on VmWare and at this time I have a problem with network. If I boot from installation CD I have a internet connection, but if I'll boot from my installation I have not the internet connection.

I noticed that if I boot from installation CD the command 'ip link' returns 'lo' and 'eth0' as network interface names, but if I'll boot from my installation 'ip link' returns 'lo' and 'enp2s1' as network interface names.

What is the reason of this difference ?

KingX · 2013-03-30 05:19:42

https://bbs.archlinux.org/viewtopic.php?id=156283

WonderWoofy · 2013-03-30 05:50:06

Just mask 80-net-name-slot.rules if you need that old naming scheme.

jasonwryan · 2013-03-30 05:51:06

Merging with the network names sticky...

arfoll · 2013-03-31 09:36:25

It seems my box on an update to systemd 198 went back to eth naming style... I'm confused!

[brendan@box1 ~]$ cat /proc/1/comm 
systemd
[brendan@box1 ~]$ pacman -Qi systemd | head -2
Name           : systemd
Version        : 198-2
[brendan@box1 ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 40:61:86:ed:62:ad brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.40/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::4261:86ff:feed:62ad/64 scope link 
       valid_lft forever preferred_lft forever
[brendan@box1 ~]$ ls -lah /etc/udev/rules.d/
total 4.0K
drwxr-xr-x 2 root root  28 Mar 30 14:20 .
drwxr-xr-x 4 root root  64 Mar 31 09:46 ..
-rw-r--r-- 1 root root 104 Mar 30 14:20 75-hdparm.rules
[brendan@box1 ~]$ uptime
 10:34:19 up 25 min,  1 user,  load average: 1.05, 1.26, 0.69

deemytch · 2013-03-31 10:33:09

Hi,all
for me the best schema to working with interfaces names is to change them forever like that

$ cat /etc/udev/rules.d/10-net.rules
SUBSYSTEM=="net", ATTR{address}=="00:23:90:a1:e5:ae", NAME="localnet"
SUBSYSTEM=="net", ATTR{address}=="00:23:90:a1:e5:af", NAME="provider0"
SUBSYSTEM=="net", ATTR{address}=="00:23:90:a1:e5:b1", NAME="provider2"
SUBSYSTEM=="net", ATTR{address}=="00:23:90:a1:e5:b0", NAME="uplink"

Hope this will help.

Last edited by deemytch (2013-03-31 10:33:47)

silentsnake · 2013-04-02 01:35:55

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.

Last edited by silentsnake (2013-04-02 01:39:59)

Arch Linux

#126 2013-02-18 19:38:56

Re: New network naming schema in systemd 197

#127 2013-02-18 19:45:52

Re: New network naming schema in systemd 197

#128 2013-02-24 18:32:31

Re: New network naming schema in systemd 197

#129 2013-02-24 22:19:44

Re: New network naming schema in systemd 197

#130 2013-02-24 22:53:23

Re: New network naming schema in systemd 197

#131 2013-02-25 01:28:09

Re: New network naming schema in systemd 197

#132 2013-02-25 02:15:53

Re: New network naming schema in systemd 197

#133 2013-02-25 13:33:02

Re: New network naming schema in systemd 197

#134 2013-03-18 19:33:40

Re: New network naming schema in systemd 197

#135 2013-03-18 19:35:02

Re: New network naming schema in systemd 197

#136 2013-03-18 22:28:06

Re: New network naming schema in systemd 197

#137 2013-03-21 00:24:56

Re: New network naming schema in systemd 197

#138 2013-03-21 00:31:30

Re: New network naming schema in systemd 197

#139 2013-03-22 04:24:06

Re: New network naming schema in systemd 197

#140 2013-03-22 04:27:18

Re: New network naming schema in systemd 197

#141 2013-03-22 04:35:27

Re: New network naming schema in systemd 197

#142 2013-03-22 04:51:31

Re: New network naming schema in systemd 197

#143 2013-03-22 07:14:11

Re: New network naming schema in systemd 197

#144 2013-03-30 05:14:56

Re: New network naming schema in systemd 197

#145 2013-03-30 05:19:42

Re: New network naming schema in systemd 197

#146 2013-03-30 05:50:06

Re: New network naming schema in systemd 197

#147 2013-03-30 05:51:06

Re: New network naming schema in systemd 197

#148 2013-03-31 09:36:25

Re: New network naming schema in systemd 197

#149 2013-03-31 10:33:09

Re: New network naming schema in systemd 197

#150 2013-04-02 01:35:55

Re: New network naming schema in systemd 197

Board footer