netctl not working some of the time

firefly431 · 2017-07-21 20:33:18

I've been having some issues with netctl. I use netctl-auto to automatically connect. It works about half the time, but fails every once in a while for various reasons and persists on reboot.

The error I'm getting now is that it connects successfully for a moment, but soon disconnects. I tried running `netctl-auto list` before, while, and after it was starting up; it successfully lists the profiles before and while it is starting up, but fails after it starts up (and has disconnected). The error message is "Failed to connect to non-global ctrl_ifname: wlp58s0 error: No such file or directory."

Here is what I think the relevant section of the journal is:

-- Unit netctl-auto@wlp58s0.service has begun starting up.
Jul 21 15:12:51 hostname netctl-auto[689]: Included profile 'utexas'
Jul 21 15:12:51 hostname netctl-auto[689]: Included profile 'myssid'
Jul 21 15:12:53 hostname avahi-daemon[244]: Joining mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.11.
Jul 21 15:12:53 hostname avahi-daemon[244]: New relevant interface wlp58s0.IPv4 for mDNS.
Jul 21 15:12:53 hostname avahi-daemon[244]: Registering new address record for 192.168.1.11 on wlp58s0.IPv4.
Jul 21 15:12:53 hostname kernel: IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
Jul 21 15:12:53 hostname wpa_actiond[707]: Starting wpa_actiond session for interface 'wlp58s0'
Jul 21 15:12:53 hostname systemd[1]: Started Automatic wireless network connection using netctl profiles.
-- Subject: Unit netctl-auto@wlp58s0.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl-auto@wlp58s0.service has finished starting up.
-- 
-- The start-up result is done.
Jul 21 15:12:53 hostname sudo[679]: pam_unix(sudo:session): session closed for user root
Jul 21 15:12:58 hostname kernel: wlp58s0: authenticate with 48:5b:39:5b:68:ad
Jul 21 15:12:58 hostname kernel: wlp58s0: send auth to 48:5b:39:5b:68:ad (try 1/3)
Jul 21 15:12:58 hostname kernel: wlp58s0: authenticated
Jul 21 15:12:58 hostname kernel: ath10k_pci 0000:3a:00.0 wlp58s0: disabling HT as WMM/QoS is not supported by the AP
Jul 21 15:12:58 hostname kernel: ath10k_pci 0000:3a:00.0 wlp58s0: disabling VHT as WMM/QoS is not supported by the AP
Jul 21 15:12:58 hostname kernel: wlp58s0: associate with 48:5b:39:5b:68:ad (try 1/3)
Jul 21 15:12:58 hostname kernel: wlp58s0: RX AssocResp from 48:5b:39:5b:68:ad (capab=0x411 status=0 aid=9)
Jul 21 15:12:58 hostname kernel: wlp58s0: associated
Jul 21 15:12:58 hostname kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready
Jul 21 15:12:58 hostname wpa_actiond[707]: Interface 'wlp58s0' connected to network 'myssid'
Jul 21 15:12:58 hostname dhcpcd[791]: DUID 00:01:00:01:20:db:51:d4:9c:b6:d0:e0:fc:a9
Jul 21 15:12:58 hostname dhcpcd[791]: wlp58s0: IAID d0:e0:fc:a9
Jul 21 15:12:59 hostname dhcpcd[791]: wlp58s0: rebinding lease of 192.168.1.11
Jul 21 15:12:59 hostname dhcpcd[791]: wlp58s0: leased 192.168.1.11 for 38400 seconds
Jul 21 15:12:59 hostname dhcpcd[791]: wlp58s0: adding route to 192.168.1.0/24
Jul 21 15:12:59 hostname dhcpcd[791]: wlp58s0: adding default route via 192.168.1.1
Jul 21 15:12:59 hostname dhcpcd[791]: forked to background, child pid 806
Jul 21 15:12:59 hostname wpa_actiond[707]: Terminating wpa_actiond session for interface 'wlp58s0'
Jul 21 15:13:00 hostname kernel: wlp58s0: deauthenticating from 48:5b:39:5b:68:ad by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 21 15:13:00 hostname avahi-daemon[244]: Interface wlp58s0.IPv4 no longer relevant for mDNS.
Jul 21 15:13:00 hostname avahi-daemon[244]: Leaving mDNS multicast group on interface wlp58s0.IPv4 with address 192.168.1.11.
Jul 21 15:13:00 hostname avahi-daemon[244]: Withdrawing address record for 192.168.1.11 on wlp58s0.
Jul 21 15:13:00 hostname dhcpcd[806]: wlp58s0: arp if_readrawpacket: Network is down
Jul 21 15:13:00 hostname dhcpcd[806]: wlp58s0: dhcp if_readrawpacket: Network is down

I am currently connected using wpa_cli directly, and it seems to be working fine.

jasonwryan · 2017-07-21 22:16:23

Please paste the output of `systemctl list-unit-files --state enabled`

firefly431 · 2017-07-21 22:19:42

Here you go:

UNIT FILE                          STATE
org.cups.cupsd.path                enabled
autovt@.service                    enabled
avahi-daemon.service               enabled
dbus-org.freedesktop.Avahi.service enabled
display-manager.service            enabled
getty@.service                     enabled
lightdm.service                    enabled
netctl-auto@.service               enabled
org.cups.cupsd.service             enabled
avahi-daemon.socket                enabled
org.cups.cupsd.socket              enabled
sshd.socket                        enabled
remote-fs.target                   enabled
fstrim.timer                       enabled

14 unit files listed.

graysky · 2017-07-21 22:24:44

I experienced similar issues a while ago and switched to systemd-networkd and haven't looked back. Doesn't directly address the cause of your issue but just a friendly suggestion.

firefly431 · 2017-07-21 22:32:21

graysky wrote:

I experienced similar issues a while ago and switched to systemd-networkd and haven't looked back. Doesn't directly address the cause of your issue but just a friendly suggestion.

Thanks! I'll look into it if I can't get it working. Do you know how to set up roaming? I'm on a laptop; I'd like to be able to connect to networks as I move between them.

eschwartz · 2017-07-21 22:44:00

systemd-networkd is AFAIK better suited to configuring wired ethernet. For WiFi I suggest you use NetworkManager, which contrary to popular belief is not just a GTK desktop applet. (I say this because in my experience one of the top reasons for people using netctl over NetworkManager is because they feel NetworkManager is too bloated.)

In fact, the applet is a thirdparty project that communicates with the NetworkManager daemon, but you can use nmcli in scripts or nmtui for an ncurses-like dialog, if you happen to prefer that.
NetworkManager seems to be the most comprehensive, powerful, and flexible tool currently available. Meanwhile, most people I know seem to feel that netctl is an ancient tool that has long since outlived its purpose and would be better off dying already and forcing people to get a modern tool (typically one of either systemd-netword, NetworkManager, or connman).

Last edited by eschwartz (2017-07-21 22:47:31)

graysky · 2017-07-21 23:13:25

Eschwartz wrote:

systemd-networkd is AFAIK better suited to configuring wired ethernet. For WiFi I suggest you use NetworkManager,

+1 ... now that I understand you use case.

Arch Linux

#1 2017-07-21 20:33:18

netctl not working some of the time

#2 2017-07-21 22:16:23

Re: netctl not working some of the time

#3 2017-07-21 22:19:42

Re: netctl not working some of the time

#4 2017-07-21 22:24:44

Re: netctl not working some of the time

#5 2017-07-21 22:32:21

Re: netctl not working some of the time

#6 2017-07-21 22:44:00

Re: netctl not working some of the time

#7 2017-07-21 23:13:25

Re: netctl not working some of the time

Board footer