Systemd network bug is driving me nuts!

[viking60]

Everybody over in the Arch forum are somewhat euphoric about systemd. It is the next big thing and good riddance of the good old rc.conf. I have danced along and thought this must be great since all the right loudmouths are so happy about it
So I am all powered by systemd now - and I am not all that happy at all. The network does simply not start. I use wlan0 and wpa_supplicant and for this systemd sux
Here is the eth bug

But it does not matter with wlan0 either. There is no problem to manually start the network with

Code: Select all

sudo systemctl start dhcpcd@wlan0

but it simply does not start at boot.

Since this is my Wifes lap I am likely to be killed if the network does not come up so I simply loose systemd and start the good old network daemon in rc.conf.
Simply because it works! ... And systemd does not

I have tried to make my own systemd services:
/etc/systemd/system/network.service

Code: Select all

[[Unit]
Description=Wireless Static IP Connectivity
Wants=network.target
Before=network.target

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network
ExecStart=/sbin/ip link set dev ${interface} up
ExecStart=/usr/sbin/wpa_supplicant -B -i ${interface} -c /etc/wpa_supplicant.conf # Remove this for wired connections
ExecStart=/sbin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev ${interface}
ExecStart=/sbin/ip route add default via ${gateway}
 
ExecStop=/sbin/ip addr flush dev ${interface}
ExecStop=/sbin/ip link set dev ${interface} down

[Install]
WantedBy=multi-user.target

And as you can se it is made a reference to /etc/conf.d/network there so I had made that too:

Code: Select all

interface=wlan0
address=192.168.0.10
netmask=24
broadcast=192.168.0.255
gateway=192.168.0.1

Enabling and starting the services ... and falling on my nose.
Frustrating indeed, but I have manual IP and networking up and running with scripts so I don't buy that systemd is better than those

Systemd has potential though and will probably work wonders in the standardisation of Linux (well with the exception of Ubuntu at this point - but their arguments do make sense to me now).
And doing a

Code: Select all

 systemctl enable "whatever service you want"

is in fact quite simple - when it works.

The big new "feature" that needs some attention is that when you do a new install with systemd it is going to invent some new names for the good old wlan0 and eth0 so your iwconfig could show something like wlp0s11 and enp0s13.

And this does matter when you want to connect to your wifi or eth But again I am a simple magazine reader - apparently that is brilliant

[dedanna1029]

I have this issue with systemd on Mageia with the wireless on my netbook, even running the netbook kernel. Played h#ll with it for days and then a fair few hours trying to get it to go, and the wireless still is not stable.

How can we switch using Mageia to rc.conf or to using some other configuration (other than systemd)? I detest systemd (and, for that matter, systemctl) - have for ages now.

P.S.: Yeeeeeeeeesss, I know what the wiki says about not using systemd, but that, as usual, is confusing to me.

[viking60]

Yes is can be a bit confusing:
Mageia1 ran on sysvinit and not systemd.
Mageia 2 switched to systemd and so did all RPM distros probably orchestrated by RedHat. Ubuntu is the only exception these days.
systemd and initscripts can run paralell so you might have a mix. Apparently the wifi problem did exist on Mageia 1 too so that should rule out systemd

To check that you are running systemd:

Code: Select all

cat /proc/1/comm

it should return systemd if that is the case.

To list running services you can do a

Code: Select all

systemctl

or

Code: Select all

systemctl list-units


It is probably not a good idea then to start the network dameon with sytstemd normally you can enable any service you want with

Code: Select all

systemctl enable <service>

and then start it with

Code: Select all

systemctl start <daemon>


It mostly works, but this software is still a baby.....growing fast though

In your case a good old netcfg might do the trick.

[dedanna1029]

Eh, we've been there done that with netcfg - also with ifconf, and all kinds of crap.

I think udev may have some play in this. For a good while, first thing that came up on boot was that udev couldn't find the ath9k module.

Maybe it's atheros. Pain in the arse, that one. Now, on top of that, they throw in systemd, and....



We r haz network of b.s., I tell ya!