You are not logged in.

Pages: 1

#1 2013-10-11 23:58:11

herOldMan
Member
Registered: 2013-10-11
Posts: 159

netctl wireless (code=exited, status=1/FAILURE)

Hi,

I am having trouble configuring netctl for wireless connections (either dynamic or static).

I have netctl working for wired networks, both dynamic and static.

I can manually connect to wireless access points.

Using a static wireless as an example, I can connect with:

sudo ip link set wlan0 down
sudo wpa_supplicant -Dwext -cbluge.conf -iwlan0 -B
sudo ip link set wlan0 up
sudo ip addr add 192.168.57.81/24 dev wlan0
sudo ip route add default via 192.168.57.1

where: bluge.conf is a file containing:

network={
	ssid="bluejayway"
	#psk="aKeyOfMine"
	psk=aHexCodeOfMine
}

My corresponding netctl profile:

#profile=bluejayway
Interface=wlan0
Connection=wireless
Security=wpa
ESSID='bluejayway'
PSK=\"aHexCodeOfMine
#Key='aKeyOfMine'
IP=static
Address='192.168.57.81/24'
Gateway='192.168.57.1'
DNS=('8.8.8.8')

Other combinations tried:

#PSK=\"aHexCodeOfMine
Key='aKeyOfMine'

PSK=\"'aHexCodeOfMine'
#Key='aKeyOfMine

PSK='aHexCodeOfMine'
#Key='aKeyOfMine''

Persistently, running:
sudo netctl start bluejayway

returns:
Job for netctl@bluejayway.service failed. See 'systemctl status netctl@bluejayway.service... details.

systemctl status:
Process: 1504 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)

journalctl -xn:
nothing relevant

Offline

#2 2013-10-12 10:45:09

David Batson
Member
Registered: 2011-10-13
Posts: 640

Re: netctl wireless (code=exited, status=1/FAILURE)

Here is what I have that works on my network:

Connection=wireless
Description='A simple WPA encrypted wireless connection'
Interface=wlan0
Security=wpa
ESSID='my_essid'
Key='96d18f3e141b30376d14f5f2120c5262b80765fde64dbc3bcb2466b355a6b37c'
IP=dhcp
# Uncomment this if your ssid is hidden
#HIDDEN=yes

Maybe you could use that as an example.

Offline

#3 2013-10-12 11:04:02

Alber
Member
From: Spain - España
Registered: 2011-11-11
Posts: 227

Re: netctl wireless (code=exited, status=1/FAILURE)

Surely you are doing this. Try the last to prevent typo errors
Try to put in PSK that you get from wpa_passphrase [ssid_name] "[pass_phrase]"

$ wpa_passphrase bluejayway 12345678
network={
	ssid="bluejayway"
	#psk="12345678"
	psk=1355f02fe14abb0a2268eaf3602cc7922c84f9112155093bd1230f4b500e6867
}

You can get it in a file with:

$ wpa_passphrase bluejayway akeyOfMine > passfile.txt

or add to a file ( >> ):

$ wpa_passphrase bluejayway akeyOfMine >> passfile.txt

Mine changing data:

Description='A simple WPA encrypted wireless connection'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='myEssid'
# 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=\"1355f02fe14abb0a2268eaf3602cc7922c84f9112155093bd1230f4b500e6867
# Uncomment this if your ssid is hidden
#Hidden=yes

Edit:
Not sure about that:
You are using google DNS: 8.8.8.8 . Could you try 192.168.57.1 ?

Edit 2:
I think your psk entry must be the key entry.

Last edited by Alber (2013-10-12 13:59:35)

Because not all of us are native English speakers, try no to use slang or abbreviations, thank you.

Offline

#4 2013-10-12 16:43:15

herOldMan
Member
Registered: 2013-10-11
Posts: 159

Re: netctl wireless (code=exited, status=1/FAILURE)

Hi,

Thanks for the replies.

My hex key is exactly correct. Dns at 192.168.57.1 did not work. (In general, I do not prefer dhcp for DNS.) I tied all recommended combinations & permutations for ESSID/ssid/Key/key/psk/PSK and punctuation inclusions. (Currently I am using the recommended syntax in "Wireless Setup.") Tried with two different wireless adaptors.

Again, manual connect using the correct ESSID and hex Key works. Manually connecting is an acceptable work-around for me. Using netctl would be better.

Offline

#5 2013-10-12 22:13:41

Alber
Member
From: Spain - España
Registered: 2011-11-11
Posts: 227

Re: netctl wireless (code=exited, status=1/FAILURE)

At risk to be annoying.
There are a lot of combinations and permutations. But Iwant to be sure:
In variable psk is the short password and in variable key the hexadecimal long one. But, I've seen in your examples, the hexadecimal long one is in psk and the short in key.

It changes from wpa_passphrase output to netctl's configuration file.

Last edited by Alber (2013-10-12 22:30:30)

Because not all of us are native English speakers, try no to use slang or abbreviations, thank you.

Offline

#6 2013-10-13 15:54:37

herOldMan
Member
Registered: 2013-10-11
Posts: 159

Re: netctl wireless (code=exited, status=1/FAILURE)

Hi,

I'm not annoyed. Sorry I'm so dunderheaded.

Here is my profile:

Connection=wireless
Interface=wlan0
Security=wpa
ESSID='bluejayway'
Key=\"d67...
#psk='aPhrase'

#Note: the router is not a dhcp server
IP=static
Address='192.168.57.23/24'
Gateway='192.168.57.1'
DNS=('8.8.8.8')

Tried this with Key/psk comments toggled and with both un-commented. During this excersize I interated over all quote formats for aPhrase as well as letter case for psk.

Also tried using this:

Connection=wireless
Interface=wlan0
Security=wpa-config
WPAConfigFile=~/manualConnect/aliant.conf
#Note: previous line was iterated over all quote formats

#Note: the router is not a dhcp server
IP=static
Address='192.168.57.23/24'
Gateway='192.168.57.1'
DNS=('8.8.8.8')

where ~/manualConnect/aliant.conf is a config file (formed with wpa-passphrase) that is known to reliably connect manually with wpa_supplicant

Offline

#7 2013-10-13 16:23:23

Alber
Member
From: Spain - España
Registered: 2011-11-11
Posts: 227

Re: netctl wireless (code=exited, status=1/FAILURE)

I never think it about somebody smile

There is the chance to use it with dhcp?
Just to reduce the boundary and be certain that the problem is in the key.
I've run out of ideas.

Surely no matter but now you are using 192.168.57.23 and before 192.168.57.81

EDIT:
I've made a test changing my profile to a static IP and it works fine.

Last edited by Alber (2013-10-13 16:50:14)

Because not all of us are native English speakers, try no to use slang or abbreviations, thank you.

Offline

#8 2013-10-13 22:33:20

mrinx
Member
From: Richmond, VA
Registered: 2013-08-01
Posts: 87
Website

Re: netctl wireless (code=exited, status=1/FAILURE)

Sometimes when I'm using netctl and systemd, I have a problem with "stucked" netctl service and then I can't connect/reconnect to the wifi. In that case it helps when I run "systemctl reset-failed" (when there is some netctl service stuck). Just saying...

English isn't my first language.
Is Arch Linux user called archer? Where are our bows and arrows?

Offline

#9 2013-10-15 20:54:19

mrinx
Member
From: Richmond, VA
Registered: 2013-08-01
Posts: 87
Website

Re: netctl wireless (code=exited, status=1/FAILURE)

herOldMan wrote:

Also tried using this:

Connection=wireless
Interface=wlan0
Security=wpa-config
WPAConfigFile=~/manualConnect/aliant.conf
#Note: previous line was iterated over all quote formats

#Note: the router is not a dhcp server
IP=static
Address='192.168.57.23/24'
Gateway='192.168.57.1'
DNS=('8.8.8.8')

where ~/manualConnect/aliant.conf is a config file (formed with wpa-passphrase) that is known to reliably connect manually with wpa_supplicant

Hmmm, have you tried this with absoluthe path to your wpaconfigfile instead of using tilde?

English isn't my first language.
Is Arch Linux user called archer? Where are our bows and arrows?

Offline

#10 2013-10-16 02:45:34

herOldMan
Member
Registered: 2013-10-11
Posts: 159

Re: netctl wireless (code=exited, status=1/FAILURE)

Yes.

I moved on. The WICD curses package manages the connection well.

Offline

Pages: 1

Board footer

Powered by FluxBB