[SOLVED] network problems moving to systemd (netcfg, ipw2100)

iemcd · 2013-01-29 14:59:50

I was moving my laptop over to systemd, and I've hit a stumbling block. Here's is what I can make of it:

1. net-auto-wireless.service fails. I understand this is a known problem, and it appears to be resolved by restarting the service after the interface appears. The other problems all come after I do this though.

2. wifi-menu reports "No networks found".

3. "iwlist eth1 scan" claims "Interface doesn't support scanning."

4. iwconfig shows that eth0 has the nickname "ipw2100" while eth1 has "no wireless extensions". (Normally eth0 is the wired interface, and eth1 is wireless. ipw2100 is, I think, the driver for my wireless chipset.)

I feel like there must just be a config file out of place or something defaulting to eth0 somewhere, but I'm honestly out of my depth here. There's a few other warnings floating around, but nothing that looks entirely relevant here.

Last edited by iemcd (2013-01-29 19:36:12)

chris_l · 2013-01-29 16:23:11

It seems ipw2100 is the new name of your wireless, but you can check it with :

iwconfig 2>&1|sed -n '/IEEE/ s/\W.*//p'

Edit /etc/conf.d/netcfg and put the correct name.

Read http://www.freedesktop.org/wiki/Softwar … rfaceNames, is probably related.

teateawhy · 2013-01-29 16:56:53

Today i added 2 lines to the beginners guide that tell you to edit /etc/conf./netcfg . I hope it is more clear now.
https://wiki.archlinux.org/index.php/Be … on#Wired_2

swordfish · 2013-01-29 17:22:32

@iemcd

Since systemd 197 all networks get persistant names. So your eth0 and eth1 will be renamend into something - well - cryptic

You can find out the new names by:

$ dmesg | grep eth1

Look for a line that reads like:

systemd-udevd[111]: renamed network interface eth1 to enp0s3

"enp0s3" is in this case just an example - yours will be called differently.

Another possibility to find out about the new names is

$ ip link

More information about this issue you will find in this posting from the arch-dev-public mailing list

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

iemcd · 2013-01-29 18:06:05

Thanks for helping me out!

If I'm getting this right, systemd uses one of the first 4 naming schemes outlined at Desktop.org, but my /etc/conf.d/netcfg file still uses "eth0" and "eth1", which aren't good anymore. So all I have to do is find out what they're actually called and put those names in the config file.

I tried using "ipw2100" in my config, but this prevents me from restarting net-auto-wireless.service because netcfg-wpa_actiond "Could not read interface ipw2100 flags: No such device", and everything else gives similar complaints. The name "nl80211", which seems somehow related does not do better.

How can I discover the names of my network interfaces then? I tried running the line above, but it gives no output (I think sed is finding no matches, but I can't quite figure out what every part is doing). Or am I misinterpreting the problem?

EDIT: Sorry, missed that last comment. I'll give that a try.

Last edited by iemcd (2013-01-29 18:06:46)

iemcd · 2013-01-29 18:23:44

@swordfish:
No such luck: dmesg does not output anything like that. Only normal-looking things and "link is not ready", which I assume is part of problem #1 in my first post.

Upon investigation, I do still have the "opt-out" file /etc/udev/rules.d/80-net-name-slot.rules. Does this imply the problem is something else, or is this itself a problem?

chris_l · 2013-01-29 18:35:34

hm, whats the output of iwconfig and ip link ?

iemcd · 2013-01-29 18:46:35

chris_l wrote:

hm, whats the output of iwconfig and ip link ?

Square brackets mark my omissions. These are after having restarted net-auto-wireless.service.

iwconfig:
irda0 no wireless extensions.
lo no wireless extensions.
eth0 unassociated ESSID:off/any Nickname:"ipw2100"
Mode:Managed Channel=0 Access Point: Not-Associated
[...7 more lines of stuff, mostly things =0...]
eth1 no wireless extensions.

ip link:
1: lo: [skipping this one]
2: irda0: [this one too]
3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
link/ether 00:0c:f1:29:32:7d brd ff:ff:ff:ff:ff:ff
4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT qlen 1000
link/ether 00:0d:60:b0:59:33 brd ff:ff:ff:ff:ff:ff

teateawhy · 2013-01-29 19:04:44

Try this script to find out the interface names:
#!/bin/bash
for i in /sys/class/net/*; do
echo "==$i"
udevadm test-builtin net_id "$i";
echo
done 2>/dev/null

chris_l · 2013-01-29 19:25:35

It seems eth0 and eth1 only switched places. You can just switch the names on the config files.

Or, if you don't like having the names like that, you can either:

delete /etc/udev/rules.d/80-net-name-slot.rules, to use the new names
Use https://wiki.archlinux.org/index.php/Ud … vice_names to assign different names to the ethernet and wifi devices

EDIT: Oh people, don't forget to put you code inside [code] tags

Last edited by chris_l (2013-01-29 19:30:22)

iemcd · 2013-01-29 19:33:59

teateawhy wrote:

Try this script to find out the interface names:

The script works, and gives me ID_NET_NAME_PATH=wlp2s2 for eth0 (which looks like my wireless) and enp2s1 for eth1 (which I assume is wired). But I plug these in and again I can no longer restart net-auto-wireless.service because there is "No such device". This still happens if I switch the two.

But I tried using the phrases "eth1" and "eth0" but switching them, and that appears to have worked (after restarting the net-auto-wireless.service). So I guess it's solved? If I were to remove the dummy rules file and change the device names to those given by the script, would this type of thing have not happened?

EDIT: Thanks Chris, I missed your post. I'll just mark this solved then.

Last edited by iemcd (2013-01-29 19:34:58)

Arch Linux

#1 2013-01-29 14:59:50

[SOLVED] network problems moving to systemd (netcfg, ipw2100)

#2 2013-01-29 16:23:11

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#3 2013-01-29 16:56:53

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#4 2013-01-29 17:22:32

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#5 2013-01-29 18:06:05

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#6 2013-01-29 18:23:44

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#7 2013-01-29 18:35:34

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#8 2013-01-29 18:46:35

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#9 2013-01-29 19:04:44

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#10 2013-01-29 19:25:35

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

#11 2013-01-29 19:33:59

Re: [SOLVED] network problems moving to systemd (netcfg, ipw2100)

Board footer