Arch Linux

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Netctl still not connecting

Hello Arch Forums!

Netctl Arch Wiki Page

I'm trying to connect to a hidden network via netctl, and eventually have it connect at startup. I copied the file form the example and ran

chmod 600 Network_I_Am_Connecting_To

I got the "Job for netctl@wlan(...).service failed" error right away. I entered the

ip link set wlan0 down

command, which seemed to be the problem according to journalctl. It seemed like it was trying to connect this time, but I got the same error.

This time, there was no solution in troubleshooting. nothing in my journalctl matched.

Here's my journalctl.

--
-- Unit netctl@Network_I_Am_Connecting_To.service has failed.
--
-- The result is failed.
Mar 02 16:50:39 My_Machine systemd[1]: Unit netctl@Network_I_Am_Connecting_To.service entered failed state.
Mar 02 16:50:39 My_Machine systemd[1]: netctl@Network_I_Am_Connecting_To.service failed.
Mar 02 16:51:31 My_Machine sudo[26676]: My_Username : TTY=pts/7 ; PWD=/home/My_Username/.config/awesome ; USER=root ; COMMAND=/usr/bin/netctl start Network_I_Am_Connecting_To
Mar 02 16:51:31 My_Machine sudo[26676]: pam_unix(sudo:session): session opened for user root by My_Username(uid=0)
Mar 02 16:51:31 My_Machine systemd[1]: Starting Networking for netctl profile Network_I_Am_Connecting_To...
-- Subject: Unit netctl@Network_I_Am_Connecting_To.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Network_I_Am_Connecting_To.service has begun starting up.
Mar 02 16:51:31 My_Machine network[26682]: Starting network profile 'Network_I_Am_Connecting_To'...
Mar 02 16:51:31 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: disabled -> inactive
Mar 02 16:51:35 My_Machine kernel: wlp2s0: authenticate with Numbers_That_Look_Important
Mar 02 16:51:35 My_Machine kernel: wlp2s0: send auth to Numbers_That_Look_Important (try 1/3)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: authenticated
Mar 02 16:51:35 My_Machine kernel: wlp2s0: associate with Numbers_That_Look_Important (try 1/3)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: RX AssocResp from Numbers_That_Look_Important (capab=Short_String_Of_Numbers status=0 aid=2)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: associated
Mar 02 16:51:35 My_Machine kernel: wlp2s0: deauthenticating from Numbers_That_Look_Important by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: inactive -> associated
Mar 02 16:51:35 My_Machine NetworkManager[286]: <warn>  Connection disconnected (reason -3)
Mar 02 16:51:35 My_Machine kernel: cfg80211: Calling CRDA to update world regulatory domain
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: associated -> disconnected
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: disconnected -> inactive
Mar 02 16:51:35 My_Machine kernel: wlp2s0: authenticate with Different_Digits_That_Look_Important
Mar 02 16:51:35 My_Machine kernel: wlp2s0: send auth to Different_Digits_That_Look_Important (try 1/3)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: authenticated
Mar 02 16:51:35 My_Machine kernel: wlp2s0: associate with Different_Digits_That_Look_Important (try 1/3)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: RX AssocResp from Different_Digits_That_Look_Important (capab=Short_String_Of_Numbers status=0 aid=6)
Mar 02 16:51:35 My_Machine kernel: wlp2s0: associated
Mar 02 16:51:35 My_Machine kernel: wlp2s0: deauthenticating from Different_Digits_That_Look_Important by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: inactive -> associated
Mar 02 16:51:35 My_Machine NetworkManager[286]: <warn>  Connection disconnected (reason -3)
Mar 02 16:51:35 My_Machine kernel: cfg80211: Calling CRDA to update world regulatory domain
Mar 02 16:51:35 My_Machine kernel: cfg80211: Calling CRDA to update world regulatory domain
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: associated -> disconnected
Mar 02 16:51:35 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: disconnected -> inactive
Mar 02 16:51:47 My_Machine network[26682]: WPA association/authentication failed for interface 'wlp2s0'
Mar 02 16:51:47 My_Machine NetworkManager[286]: <info>  (wlp2s0): supplicant interface state: inactive -> disabled
Mar 02 16:51:47 My_Machine network[26682]: Failed to bring the network up for profile 'Network_I_Am_Connecting_To'
Mar 02 16:51:47 My_Machine systemd[1]: netctl@Network_I_Am_Connecting_To.service: main process exited, code=exited, status=1/FAILURE
Mar 02 16:51:47 My_Machine systemd[1]: Failed to start Networking for netctl profile Network_I_Am_Connecting_To.
-- Subject: Unit netctl@Network_I_Am_Connecting_To.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Network_I_Am_Connecting_To.service has failed.
--
-- The result is failed.
Mar 02 16:51:47 My_Machine systemd[1]: Unit netctl@Network_I_Am_Connecting_To.service entered failed state.
Mar 02 16:51:47 My_Machine systemd[1]: netctl@Network_I_Am_Connecting_To.service failed.
Mar 02 16:51:47 My_Machine sudo[26676]: pam_unix(sudo:session): session closed for user root
Mar 02 16:52:04 My_Machine /etc/gdm/Xsession[7218]: Warning: Cannot convert string "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*" to type FontStruct

And here's my network profile:

Description='Network_I_Am_Connecting_To'
Interface=wlp2s0
Connection=wireless

Security=wpa
IP=dhcp

ESSID='Network_I_Am_Aonnecting_To'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='My_Network_Password'
# Uncomment this if your ssid is hidden
scan_ssid=1
Hidden=yes
# Set a priority for automatic profile selection
#Priority=10

Any solutions?

Last edited by SwitchDhole (2015-03-12 15:16:39)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Netctl still not connecting

Can you connect manually? It's definitely the best way to debug wifi stuff.

Also, there are other utilities available as well as netctl - unless you're particularly attached to it, I'd try (some of) them out.

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: Netctl still not connecting

You seem to be running NetworkManager and using netctl at the same time, and that that's causing the errors

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

tomk : I can try to connect manually, but when I get to

iw dev wlan0 scan | less

I get the message

command failed: Device or resource busy (-16)

I will try set up my network connection manually.

/hbar : The above seems to go with what you wrote.  Entering

nmcli r wifi on

Didn't fix the problem. How do I stop NetworkManager?

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: Netctl still not connecting

Stop and disable the NetworkManager.service via systemctl

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Still Failed

Here's my output. Any other Ideas?

-- Unit NetworkManager.service has finished shutting down.
Mar 03 18:32:04 archbox sudo[20533]: pam_unix(sudo:session): session closed for user root
Mar 03 18:33:12 archbox sudo[20585]: switch : TTY=pts/0 ; PWD=/home/switch/Downloads/prboom-2.5.0 ; USER=root ; COMMAND=/usr/bin/netctl start Network_I_Am_Connecting_To
Mar 03 18:33:12 archbox sudo[20585]: pam_unix(sudo:session): session opened for user root by switch(uid=0)
Mar 03 18:33:12 archbox systemd[1]: Starting Networking for netctl profile Network_I_Am_Connecting_To...
-- Subject: Unit netctl@Network_I_Am_Connecting_To.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Network_I_Am_Connecting_To.service has begun starting up.
Mar 03 18:33:12 archbox network[20591]: Starting network profile 'Network_I_Am_Connecting_To'...
Mar 03 18:33:13 archbox kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Mar 03 18:33:29 archbox network[20591]: WPA association/authentication failed for interface 'wlp2s0'
Mar 03 18:33:29 archbox network[20591]: Failed to bring the network up for profile 'Network_I_Am_Connecting_To'
Mar 03 18:33:29 archbox systemd[1]: netctl@Network_I_Am_Connecting_To.service: main process exited, code=exited, status=1/FAILURE
Mar 03 18:33:29 archbox systemd[1]: Failed to start Networking for netctl profile Network_I_Am_Connecting_To.
-- Subject: Unit netctl@Network_I_Am_Connecting_To.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@Network_I_Am_Connecting_To.service has failed.
--
-- The result is failed.
Mar 03 18:33:29 archbox systemd[1]: Unit netctl@Network_I_Am_Connecting_To.service entered failed state.
Mar 03 18:33:29 archbox systemd[1]: netctl@Network_I_Am_Connecting_To.service failed.
Mar 03 18:33:29 archbox sudo[20585]: pam_unix(sudo:session): session closed for user root
Mar 03 18:35:19 archbox sudo[21088]: switch : TTY=pts/0 ; PWD=/etc/netctl ; USER=root ; COMMAND=/usr/bin/netctl start wlp2s0-Network_I_Am_Connecting_To
Mar 03 18:35:19 archbox sudo[21088]: pam_unix(sudo:session): session opened for user root by switch(uid=0)
Mar 03 18:35:19 archbox systemd[1]: Starting Networking for netctl profile wlp2s0-Network_I_Am_Connecting_To...
-- Subject: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has begun starting up.
Mar 03 18:35:19 archbox network[21095]: Starting network profile 'wlp2s0-Network_I_Am_Connecting_To'...
Mar 03 18:35:19 archbox kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Mar 03 18:35:35 archbox network[21095]: WPA association/authentication failed for interface 'wlp2s0'
Mar 03 18:35:35 archbox network[21095]: Failed to bring the network up for profile 'wlp2s0-Network_I_Am_Connecting_To'
Mar 03 18:35:35 archbox systemd[1]: netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service: main process exited, code=exited, status=1/FAILURE
Mar 03 18:35:35 archbox systemd[1]: Failed to start Networking for netctl profile wlp2s0-Network_I_Am_Connecting_To.
-- Subject: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has failed.
--
-- The result is failed.
Mar 03 18:35:35 archbox systemd[1]: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service entered failed state.
Mar 03 18:35:35 archbox systemd[1]: netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service failed.
Mar 03 18:35:35 archbox sudo[21088]: pam_unix(sudo:session): session closed for user root

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: Netctl still not connecting

Is wlp2s0 down?

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

iw dev wlp2s0 link

and

iw dev wlp2s0 scan

tell me wlp2s0 is up and giving proper output. The latter lists the networks around me.

Both

netctl start Network_I_Am_Connecting_To

(profile I made)
and

netctl start wlp2s0-Network_I_Am_Connecting_To

(profile automatically generated by NetworkManager in GNOME) give the same output when running

netctl start wireless-wpa

Last edited by SwitchDhole (2015-03-03 18:53:39)

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: Netctl still not connecting

wlp2s0 should be down before running netctl

ip link set wlp2s0 down

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Stopped NetworkManager.service, disabled it, and set wlp2s0 down. Still didn't connect.

Here's the output:

Mar 04 18:23:44 archbox sudo[3038]: pam_unix(sudo:session): session opened for user root by switch(uid=0)
Mar 04 18:23:44 archbox systemd[1]: Starting Networking for netctl profile wlp2s0-Network_I_Am_Connecting_To...
-- Subject: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has begun starting up.
Mar 04 18:23:44 archbox systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Mar 04 18:23:44 archbox network[3045]: Starting network profile 'wlp2s0-Network_I_Am_Connecting_To'...
Mar 04 18:23:44 archbox kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Mar 04 18:24:00 archbox network[3045]: WPA association/authentication failed for interface 'wlp2s0'
Mar 04 18:24:00 archbox network[3045]: Failed to bring the network up for profile 'wlp2s0-Network_I_Am_Connecting_To'
Mar 04 18:24:00 archbox sudo[3038]: pam_unix(sudo:session): session closed for user root
Mar 04 18:24:00 archbox systemd[1]: netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service: main process exited, code=exited, status=1/FAILURE
Mar 04 18:24:00 archbox systemd[1]: Failed to start Networking for netctl profile wlp2s0-Network_I_Am_Connecting_To.
-- Subject: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service has failed.
--
-- The result is failed.
Mar 04 18:24:00 archbox systemd[1]: Unit netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service entered failed state.
Mar 04 18:24:00 archbox systemd[1]: netctl@wlp2s0\x2dNetwork_I_Am_Connecting_To.service failed.

I don't know what else to do.

weirddan455

Member

Registered: 2012-04-15

Posts: 209

Re: Netctl still not connecting

A developer told me on IRC a while back that netctl is more or less depreciated.  He was encouraging people to use systemd-networkd instead.  Maybe give that a shot?  Sorry I can't really be of more help because I don't use netctl or wireless.

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: Netctl still not connecting

netctl is a collection of shell scripts that use ip and wpa_supplicant, so I doubt its deprecated.

What wireless card do you have and what driver do you use? Did you check that two conflicting modules aren't loaded at the same time?

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

I'm using an Asrock FM2A88X-ITX+ motherboard, which has built-in wifi and bluetooth. I didn't install a wifi driver, just 'gnome', and off from there.

Wifi connects automatically in 'gnome' as it should, but I have to re-enter the password in 'nmtui' to get connected in 'awesome', even though I have it set to connect automatically under 'edit connection'.

Perhaps I should just start this wifi thing over and configure it manually.

Last edited by SwitchDhole (2015-03-09 17:50:40)

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

I can try to connect to a network manually, but when I reach

# wpa_supplicant -D nl80211,wext -i wlan0 -c <(wpa_passphrase "your_SSID" "your_key")

I get

Successfully initialized wpa_supplicant
Failed to open config file '/dev/fd/63', error: No such file or directory
Failed to read or parse configuration '/dev/fd/63'.

I can give more info, if needed

Last edited by SwitchDhole (2015-03-09 18:10:03)

Tutti

Member

Registered: 2015-02-26

Posts: 117

Re: Netctl still not connecting

I can try to connect to a network manually, but when I reach

Successfully initialized wpa_supplicant
Failed to open config file '/dev/fd/63', error: No such file or directory
Failed to read or parse configuration '/dev/fd/63'.

You can try

# wpa_passphrase > filename
# wpa_supplicant -D nl80211,wext -i wlp2s0 -c filename

which should work.
* replace filename with a filename of your choosing...

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

You can try

# wpa_passphrase > filename
# wpa_supplicant -D nl80211,wext -i wlp2s0 -c filename

which should work.
* replace filename with a filename of your choosing...

The first thing I did was stop NetworkManager.

Then I entered

sudo wpa_passphrase > network

Which didn't give any output.
Then I entered

sudo wpa_supplicant -D nl80211,wext -i wlp2s0 -c network

giving off

Successfully initialized wpa_supplicant
Line 1: unknown global field 'usage: wpa_passphrase <ssid> [passphrase]'.
Line 1: Invalid configuration line 'usage: wpa_passphrase <ssid> [passphrase]'.
Line 3: unknown global field 'If passphrase is left out, it will be read from stdin'.
Line 3: Invalid configuration line 'If passphrase is left out, it will be read from stdin'.
Failed to read or parse configuration '/home/switch/network'.

Was there a config file I was supposed to create?

Last edited by SwitchDhole (2015-03-10 14:55:55)

Tutti

Member

Registered: 2015-02-26

Posts: 117

Re: Netctl still not connecting

You can try

# wpa_passphrase > filename

Successfully initialized wpa_supplicant
Line 1: unknown global field 'usage: wpa_passphrase <ssid> [passphrase]'.
Line 1: Invalid configuration line 'usage: wpa_passphrase <ssid> [passphrase]'.
Line 3: unknown global field 'If passphrase is left out, it will be read from stdin'.
Line 3: Invalid configuration line 'If passphrase is left out, it will be read from stdin'.
Failed to read or parse configuration '/home/switch/network'.

Was there a config file I was supposed to create?

Sorry, it should have been:

#wpa_passphrase ssid "passphrase" > filename

which would create a config new file in your current directory containing the ssid of the network to connect to and the passphrase.

But you got NetworkManager to work, as wanted in Gnome?
With the inconvenience of retyping the passphrase in nmtui under awesome?
I would suggest trying to find out how to fix the issue with nmtui not remembering the password.

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

I'm making progress, but now it just hangs on

Successfully initialized wpa_supplicant

Still no connection.
Perhaps this is because this is a hidden network I'm connecting to.

As for why I'm not using networkmanager, I want less reliance on gnome, the network to connect on login, and to connect to the desired network when making a new installation (hidden networks don't work in wifi-menu). Plus, It's better to manually connect, so I've heard.

Tutti

Member

Registered: 2015-02-26

Posts: 117

Re: Netctl still not connecting

Add the '-B' switch to the wpa_supplicant line you've used (runs it in the background) and continue with the wiki

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Not quite there yet

I still didn't get connected.

For troubleshooting, I won't run it in the background. For now.

I took a look at the

network

file I made. It looked like

network={
        ssid="Network_I_Am_Connecting_To"
        #psk="Wifi_Key"
        psk=27bef67e26069e38d40aec5981b47431bf442f2b76b84539d51edc8996548faa
}

I added

scan_ssid=1

after "ssid".

Now I get

Successfully initialized wpa_supplicant
wlp2s0: SME: Trying to authenticate with String_Of_Numbers (SSID='Network_I_Am_Connecting_To' freq=2437 MHz) 
wlp2s0: Trying to associate with String_Of_Numbers (SSID='Network_I_Am_Connecting_To' freq=2437 MHz)
wlp2s0: Associated with String_Of_Numbers 
wlp2s0: WPA: Key negotiation completed with String_Of_Numbers [PTK=CCMP GTK=TKIP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to String_Of_Numbers completed [id=0 id_str=]

which looks great, but when I try to browse in firefox I get the "Server not found" screen.

Still no internet access. Is this why you linked to getting an ip address? I know little about networking and I have to switch utilities every time I post.

Last edited by SwitchDhole (2015-03-11 17:23:36)

Tutti

Member

Registered: 2015-02-26

Posts: 117

Re: Netctl still not connecting

When you complete the wpa_supplicant step you're connected to the access point, but your computer will not have an IP address assigned (thus not able to browse the internet).
From the output you posted, it looks like you have successfully connected to the AP, and only require an IP.

since you don't background the wpa_supplicant process:
1- open a new terminal without closing the old one
2- perform the step to get an IP-address, wait for it to complete

You can remove the commented (#) psk line with the clear format passphrase from the file

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Awesome! I'm connected!

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Oh, there's just one last thing:
I want the network to connect automatically at startup.

I've created the systemd unit, which looks like this:

[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/Network_I_Am_Connecting_To
ExecStart=/usr/bin/dhcpcd %i

ExecStop=/usr/bin/ip link set dev %i down

[Install]
WantedBy=multi-user.target

Entering

sudo systemctl start network-wireless@wlp2s0.service

works great, but on startup I get the message:

[FAILED] Failed to start wireless network connectivity (wlp2s0)
See "systemctl status network-wireless@wlp2s0.service" for details.

I checked it out, which gave me this:

systemctl -l  status network-wireless@wlp2s0.service
● network-wireless@wlp2s0.service - Wireless network connectivity (wlp2s0)
   Loaded: loaded (/etc/systemd/system/network-wireless@.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2015-03-12 16:01:24 CET; 6min ago
  Process: 406 ExecStart=/usr/bin/dhcpcd %i (code=exited, status=1/FAILURE)
  Process: 402 ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/Network_I_Am_Connecting_To (code=exited, status=0/SUCCESS)
  Process: 367 ExecStart=/usr/bin/ip link set dev %i up (code=exited, status=0/SUCCESS)
 Main PID: 406 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/system-network\x2dwireless.slice/network-wireless@wlp2s0.service

Mar 12 16:01:23 archbox systemd[1]: Starting Wireless network connectivity (wlp2s0)...
Mar 12 16:01:25 archbox dhcpcd[406]: dhcpcd[406]: dhcpcd already running on pid 368 (/run/dhcpcd-wlp2s0.pid)

What is

code=exited

and how can I fix it?

Tutti

Member

Registered: 2015-02-26

Posts: 117

Re: Netctl still not connecting

Mar 12 16:01:25 archbox dhcpcd[406]: dhcpcd[406]: dhcpcd already running on pid 368 (/run/dhcpcd-wlp2s0.pid)

you already had dhcpcd running, I assume you connected manually first and then tried to start the unit.
Try killing the process or reboot, and then try to start the unit

SwitchDhole

Member

Registered: 2015-02-01

Posts: 51

Re: Netctl still not connecting

Killed the process, rebooted, still getting failure.

I even disabled dhcpcd (my systemctl unit starts it anyway) and rebooted again and got the same failure message.

Last edited by SwitchDhole (2015-03-12 16:48:15)