You are not logged in.

#1 2013-01-16 18:15:53

nolsen01
Member
Registered: 2010-05-25
Posts: 8

New network naming schema in systemd 197

The liveCD was able to use eth0 just fine. I installed the system and configured it but after rebooting, I have not connection and 'ip addr' only shows "1: lo", no eth0.

I have an intel chipset which apparently used e1000e. Which appears to be loaded, but you tell me:




[root@Strongarm ~]# dmesg | grep e1000e

e1000e: Intel (R)_ PRO/1000 Network Driver - 2.0.0-k
e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
e1000e: 0000:00:19.0: setting latency timer to 64
e1000e: 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e: 0000:00:19.0: irq 45 for MSI/MSI-X
e1000e: 0000:00:19.0: eth0 (PCI Express: 2.5GT/s:Width x1) 00:16:76:c8:76:6e
e1000e: 0000:00:19.0: eth0 Intel(R) PRO/1000 Network Connection
e1000e: 0000:00:19.0: eth0: MAC: 6, PHY: 6, PBA No: FFFFFF-OFF





I'm not too sure where to go from here. Please let me know what you need. smile


# Mod edit: stickying this until is passes through

Last edited by jasonwryan (2013-01-17 23:08:34)

Offline

#2 2013-01-16 18:25:36

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,585

Re: New network naming schema in systemd 197

Hint: ip addr doesn't show non-configured interfaces.


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#3 2013-01-16 18:44:55

chris_l
Member
Registered: 2010-12-01
Posts: 387

Re: New network naming schema in systemd 197

Since the live cd detected eth0, is probably is related to this:
http://www.freedesktop.org/wiki/Softwar … rfaceNames

Last edited by chris_l (2013-01-16 18:45:06)


"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.

Offline

#4 2013-01-16 18:46:43

LinuxFun0000
Member
From: Ottawa, Canada
Registered: 2013-01-16
Posts: 4

Re: New network naming schema in systemd 197

Just a guess but I think I had the same issue. Somewhere in dmesg after the NIC is initialized, Systemd/UDev changes the name of Eth0 to something persistent. This is a new thing that was just updated and affects new installs.

https://mailman.archlinux.org/pipermail … 24231.html

Try this to see if it fixes the issue:

ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

If this doesn't fix it or this isn't the issue, you can just delete the created symlink.

Hope this helps.

Edit: And Chris_l types faster than I can smile

Last edited by LinuxFun0000 (2013-01-16 18:47:36)

Offline

#5 2013-01-16 18:54:23

nolsen01
Member
Registered: 2010-05-25
Posts: 8

Re: New network naming schema in systemd 197

Alphaniner: Thanks for the hint. I used the Network Configuration Archwiki page and this page..

'ip link' shows two other interfaces. enp0s25, and wlp6s0 - both down. So:

ip link set enp0s25 up
systemctl start dhcpcd@enp0s25

worked!

Thanks to chris_l and linux fun as well. I think you guys are correct, I will try the symbolic link trick and see what happens.

Am I going to have to do this everytime I boot up?

Offline

#6 2013-01-16 18:55:01

LinuxFun0000
Member
From: Ottawa, Canada
Registered: 2013-01-16
Posts: 4

Re: New network naming schema in systemd 197

After reading through the forums the past little while, there seems to be a recurring theme for some new users (myself included) with not being able to connect to a network after a fresh install. After not being able to find the answer myself after multiple searches, I would like to thank the people on #archlinux irc group who pointed me in the right direction.

So to help others that are having the same issue, here is the information required. (I apologize if this is the wrong area to post this)

https://mailman.archlinux.org/pipermail … 24231.html

The issue stems from the newest update to the systemd package. With this release, the upstream maintainer has changed the way that network devices get assigned names. They have switch to a persistent naming scheme and sometime after the NIC is initialized, UDev will change the name from eth0 to something else.

The quick fix to disable this feature and go back to the standard eth0 is as follows:

ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

I am not sure if this is the best solution, but as I only have the one NIC in my machine, it works for me.

Hope this helps people.

Offline

#7 2013-01-16 18:56:42

LinuxFun0000
Member
From: Ottawa, Canada
Registered: 2013-01-16
Posts: 4

Re: New network naming schema in systemd 197

nolsen01 wrote:

Alphaniner: Thanks for the hint. I used the Network Configuration Archwiki page and this page..

'ip link' shows two other interfaces. enp0s25, and wlp6s0 - both down. So:

ip link set enp0s25 up
systemctl start dhcpcd@enp0s25

worked!

Thanks to chris_l and linux fun as well. I think you guys are correct, I will try the symbolic link trick and see what happens.

Am I going to have to do this everytime I boot up?

No. The symlink trick will fix it for every boot.

Last edited by LinuxFun0000 (2013-01-16 18:58:12)

Offline

#8 2013-01-16 19:39:47

chris_l
Member
Registered: 2010-12-01
Posts: 387

Re: New network naming schema in systemd 197

nolsen01 wrote:

I will try the symbolic link trick and see what happens.

Since the new devices names from now on is going to be things like enp0s25, and the symlink is just a way to use the legacy names, I would recommend you to stick with the new names instead of doing the symlink thing.


"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.

Offline

#9 2013-01-16 19:42:45

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,134
Website

Re: New network naming schema in systemd 197

LinuxFun000 wrote:

After reading through the forums the past little while, there seems to be a recurring theme for some new users (myself included) with not being able to connect to a network after a fresh install. After not being able to find the answer myself after multiple searches, I would like to thank the people on #archlinux irc group who pointed me in the right direction....

Hope this helps people.

This sort of thing is better suited to the wiki.

Posting here, with your title, implies a problem. For the vast majority of users, they will have read the ML and the post-install note and will have made the adjustment to their system (including alternate solutions to the one you posted).


Merging...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#10 2013-01-16 20:27:11

2k
Member
From: UK
Registered: 2006-02-17
Posts: 75

Re: New network naming schema in systemd 197

Hi there

I have recently installed arch onto an old computer to use as a router, however after installation I couldn't get connected to the wifi, after further investigation it seems that rather than call the interfaces wlan0 and eth0 as they have been called during the install and when using other distro's on this machine, for some reason it is calling them wlp0s11 for the wlan0 and enp0s13 for eth0

when I tried to connect to the wifi using wlp0s11 it worked, but I don't like the names of the interfaces like this.

I'm just hoping someone knows what I have done wrong and can help me get it back to as it should be

here is the output of iwconfig with wlp0s11 connected to the wifi

# iwconfig
wlp0s11   IEEE 802.11bg  ESSID:"MyWifi"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:17:3F:4B:A6:C0   
          Bit Rate=1 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:4  Invalid misc:66   Missed beacon:0

lo        no wireless extensions.

enp0s13   no wireless extensions.

Thanks for anyones suggestions

Mike

Offline

#11 2013-01-16 20:31:09

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 4,717

Re: New network naming schema in systemd 197

You didn't do anything wrong, this is a new feature in systemd 197. There are a number of threads mentioning it already.

Offline

#12 2013-01-16 20:32:48

swordfish
Member
Registered: 2012-01-14
Posts: 160

Re: New network naming schema in systemd 197

You did nothing wrong wink . This is default behaviour for new installs since systemd 197.

For more info please read: https://mailman.archlinux.org/pipermail … 24231.html


Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)

Offline

#13 2013-01-16 20:33:20

2k
Member
From: UK
Registered: 2006-02-17
Posts: 75

Re: New network naming schema in systemd 197

Oh sorry, I did a google search for the word wlp0s11 and it drew a blank. Can you link me to an article about it? I wonder why its changed, wlan0 and eth0 looked so much nicer sad

Offline

#14 2013-01-16 20:35:28

2k
Member
From: UK
Registered: 2006-02-17
Posts: 75

Re: New network naming schema in systemd 197

Thanks swordfish,

sorry to have repeated a thread sad

Offline

#15 2013-01-16 20:35:41

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: New network naming schema in systemd 197

edit: deleted/double-post to swordfish

Last edited by Strike0 (2013-01-16 20:37:30)

Offline

#16 2013-01-16 20:36:55

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,134
Website

Re: New network naming schema in systemd 197

Merging...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#17 2013-01-16 21:07:19

GalacticArachnid
Member
Registered: 2009-01-02
Posts: 155
Website

Re: New network naming schema in systemd 197

Reinstalled Arch today, the live cd presented my network interface(s) in a sane fashion such as eth0. The installed system however seems to have regressed to enp0s6.

Can I fix this?
Will I have to use udev rules? If so, why?
Whats causing my network devices to have such names?

Offline

#18 2013-01-16 21:12:53

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,134
Website

Re: New network naming schema in systemd 197

Merging with the established thread...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#19 2013-01-17 07:07:36

the sad clown
Member
From: 192.168.0.X
Registered: 2011-03-20
Posts: 833

Re: New network naming schema in systemd 197

I've been having some trouble with this.  I have a AR9285 using ath9k.  I've tried

ip link set wlp2s0 up

But it does nothing.  No error message, but no interface is brought up.  'ip addr show' still only shows lo.  I checked and the driver is loading fine.  I've also confirmed that wlp2s0 is the correct interface name under the new scheme using

for i in /sys/class/net/*; do
    echo "==$i"
    udevadm test-builtin net_id "$i";
    echo
done 2>/dev/null

What am I forgetting to do?


I laugh, yet the joke is on me

Offline

#20 2013-01-17 07:12:01

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,134
Website

Re: New network naming schema in systemd 197

What does ifconfig -a show as the devices?


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#21 2013-01-17 07:21:28

chris_l
Member
Registered: 2010-12-01
Posts: 387

Re: New network naming schema in systemd 197

the sad clown wrote:

I've been having some trouble with this.  I have a AR9285 using ath9k.  I've tried

ip link set wlp2s0 up

But it does nothing.  No error message, but no interface is brought up.  'ip addr show' still only shows lo.  I checked and the driver is loading fine.  I've also confirmed that wlp2s0 is the correct interface name under the new scheme using

for i in /sys/class/net/*; do
    echo "==$i"
    udevadm test-builtin net_id "$i";
    echo
done 2>/dev/null

What am I forgetting to do?

Doing 'ip addr show' will only show you devices with IP addresses. Do 'ip link' instead to show all interfaces, including the ones without IP.
Just bringing up an interface wont give you an IP address. You need to reconfigue netcfg or wicd or whatever you use to connect to the wireless and tell it to use wlp2s0 instead of wlan0 (or whatever you had before).
EDIT: Fixed that wiki article.

Last edited by chris_l (2013-01-17 17:30:23)


"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.

Offline

#22 2013-01-17 16:30:23

the sad clown
Member
From: 192.168.0.X
Registered: 2011-03-20
Posts: 833

Re: New network naming schema in systemd 197

Thanks for the help.  I followed the wiki for enabling network interfaces and it told me to use ip addr to check the results for 'ip link set xxx up'.  Since I didn't get good results from that I didn't proceed further.  You were right Chris_I.  I just ignored it and reconfigured netcfg and everything worked fine.  Thanks again.


I laugh, yet the joke is on me

Offline

#23 2013-01-17 23:05:39

Zerathidune
Member
Registered: 2007-02-25
Posts: 101

Re: New network naming schema in systemd 197

Hey,

I just picked up a new laptop and set up arch on it. I'm having what I consider to be a very strange issue: My network interface names are not always the same on boot. sometimes I get the typical wlan0/eth0/lo set, but just as often I get the following:

enp0s25   no wireless extensions.

wlp3s0    IEEE 802.11abgn  ESSID:"censored"  
          Mode:Managed  Frequency:2.432 GHz  Access Point: 00:CE:41:50:17:ED   
          Bit Rate=54 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=51/70  Signal level=-59 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:115   Missed beacon:0

lo        no wireless extensions.

Sometimes just one of them has an atypical name.

This is mostly just weird, but it does cause some configuration headaches, so I'd like to fix it. In particular, when the above happens, connman thinks that wlp3s0 isn't wireless, and so I can't use it to choose an ssid (using connmanctl as a frontend).

I found the following in my dmesg:

[    3.316821] systemd-udevd[133]: renamed network interface wlan0 to wlp3s0

There's a similar line for the other interface. This is probably the culprit, but I have no idea *why* it's happening, or exactly what to do about it.

Here's my lscpi output, in case it is useful:

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT IDER Controller (rev 07)
00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection

Some advice would be appreciated, thank in advance.

Offline

#24 2013-01-17 23:06:54

jasonwryan
Forum & Wiki Admin
From: .nz
Registered: 2009-05-09
Posts: 18,134
Website

Re: New network naming schema in systemd 197

Merging with the pre-existing thread...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#25 2013-01-17 23:14:19

Zerathidune
Member
Registered: 2007-02-25
Posts: 101

Re: New network naming schema in systemd 197

Ack, Sorry. Names like these are hard to search for.

Offline

Board footer

Powered by FluxBB