Arch Linux

SebastianDen98onde

Member

Registered: 2017-03-23

Posts: 1

"Netctl start interface" stopped working all of the sudden

From journalctl -xe :

-- The start-up result is done.
Mar 23 19:50:18 SchulerComp systemd[1]: Starting Networking for netctl profile Home...
-- Subject: Unit netctl@Home.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Home.service has begun starting up.
Mar 23 19:50:18 SchulerComp network[1295]: Starting network profile 'Home'...
Mar 23 19:50:18 SchulerComp network[1295]: DEBUG: wpa_start: wpa_supplicant -q -B -P /run/wpa_supplicant_wlp3s0.pid -i wlp3s0-D nl80211,wext -c/run/network/wpa_supplicant_wlp3s0.conf

Mar 23 19:50:23 SchulerComp network[1295]: Failed to bring the network up for profile 'Home'...
Mar 23 19:50:23 SchulerComp systemd[1]: netctl@Home.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 19:50:23 SchulerComp systemd[1]: Failed to start Networking for netctl profile Home.
-- Subject: Unit netctl@Home.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Home.service has failed.
--
-- The result is failed.
Mar 23 19:50:23 SchulerComp systemd[1]: netctl@Home.service: Unit entered failed state.
Mar 23 19:50:23 SchulerComp systemd[1]: netctl@Home.service: Failed with result 'exit-code'.
Mar 23 19:50:23 SchulerComp polkitd[524]: Unregistered Authentication Agent for unix-process:1286:59634 (system bus name :1.51, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

###
I've googled a lot without any results. Any suggestions?

Last edited by SebastianDen98onde (2017-03-23 20:05:49)

alaskanarcher

Member

Registered: 2016-04-30

Posts: 50

Re: "Netctl start interface" stopped working all of the sudden

Try bringing the wireless interface down and calling 'netctl stop-all' before trying to start a profile with netctl. Netctl will set the interface back up for you.

# ip link set wlp2s0 down
# netctl stop-all
# netctl start home

I use netctl for configuring my wireless interface. In my experience it can be a little finicky. If the wireless interface is not in a state that netctl expects, it just stops and the logging doesn't offer a lot of helpful information. If I had to guess I'd bet this is done intentionally with the idea that netctl calls should not try and make anything work, but rather netctl should try to do exactly what it was asked and if it can't, just stop and let the user figure it out.

I personally like this about it, since I don't leave profiles enabled so as to have to be explicit about what wireless networks I join.

Check out NetworkManager if you want a more complete and user friendly interface with nice GUIs available.