Arch Linux

FlowIt

Member

Registered: 2014-10-25

Posts: 239

Slow netctl boot after using networkd

I tried out systemd-networkd but switched back to netctl a few days later. enp2s0 is both my interface and the name of my profile in netctl. The steps I did:

netctl stop enp2s0
netctl disable enp2s0
// create /etc/systemd/network/wired.network as in the wiki
systemctl enable systemd-networkd.service
systemctl enable systemd-resolved.service
systemctl reboot
// few days pause, without any system updates or changes
systemctl stop systemd-resolved.service
systemctl stop systemd-networkd.service
systemctl disable systemd-resolved.service
systemctl disable systemd-networkd.service
netctl enable enp2s0
systemctl reboot

I am using dhcp with dhcpcd as my client. systemd-analyze blame shows the startup of the enp2s0 profile takes between 8 and 10 seconds, but it was at most 1.5 seconds before.

The output of journalctl -b -u netctl@enp2s0.service

-- Logs begin at Fri 2016-07-22 13:51:20 CEST, end at Sun 2016-07-24 18:04:58 CEST. --
Jul 24 17:50:08 me systemd[1]: Starting Wired...
Jul 24 17:50:08 me network[326]: Starting network profile 'enp2s0'...
Jul 24 17:50:11 me dhcpcd[358]: DUID 00:01:00:01:1b:ec:16:f0:e8:11:32:6c:9e:77
Jul 24 17:50:11 me dhcpcd[358]: enp2s0: IAID 32:6c:9e:77
Jul 24 17:50:11 me dhcpcd[358]: enp2s0: rebinding lease of 192.168.178.30
Jul 24 17:50:11 me dhcpcd[358]: enp2s0: probing address 192.168.178.30/24
Jul 24 17:50:17 me dhcpcd[358]: enp2s0: leased 192.168.178.30 for 864000 seconds
Jul 24 17:50:17 me dhcpcd[358]: enp2s0: adding route to 192.168.178.0/24
Jul 24 17:50:17 me dhcpcd[358]: enp2s0: adding default route via 192.168.178.1
Jul 24 17:50:17 me network[326]: Started network profile 'enp2s0'
Jul 24 17:50:17 me systemd[1]: Started Wired.

and finally the netctl profile /etc/netctl/enp2s0:

Description='Wired'
Interface=enp2s0
Connection=ethernet
IP=dhcp

So I am out of ideas where to look and what to try. Any help is greatly appreciated.

Last edited by FlowIt (2016-07-24 16:11:30)