You are not logged in.

Pages: 1

#1 2013-06-14 11:53:14

thall
Member
Registered: 2012-05-30
Posts: 12

netctl and WPA2 Personal AES, problem with authentication

I having trouble to connect to my WPA2 Personal 5ghz wireless AES (only) network using netctl. When I were using wicd it wasnt any problems. I assume there is something wrong in my profile but i cant find out what.

My config /etc/netctl/wlp4s0-limbo2

Description='A wireless connection using a custom network block configuration'
Interface=wlp4s0    
Connection=wireless    
Security=wpa-configsection
IP=dhcp             
WPAConfigSection=(     
    'ssid="limbo"'  
    'key_mgmt=WPA-PSK' 
    'proto=RSN'    
    'pairwise=CCMP'    
    'group=CCMP'    
    'psk="key"'                                                         
)

and this is the output from journalctl -xn

Error was encountered while opening journal files: No data available
-- Logs begin at Mon 2001-01-01 01:02:40 CET, end at Fri 2013-06-14 13:45:30 CEST. --
Jun 14 13:45:14 thallarch sudo[18463]: thall : TTY=pts/3 ; PWD=/home/thall ; USER=root ; COMMAND=/usr/bin/netctl start wlp4s0-limbo2
Jun 14 13:45:14 thallarch sudo[18463]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 14 13:45:14 thallarch systemd[1]: Starting Networking for netctl profile wlp4s0-limbo2...
-- Subject: Unit netctl@wlp4s0\x2dlimbo2.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp4s0\x2dlimbo2.service has begun starting up.
Jun 14 13:45:14 thallarch network[18470]: Starting network profile 'wlp4s0-limbo2'...
Jun 14 13:45:30 thallarch network[18470]: WPA association/authentication failed for interface 'wlp4s0'
Jun 14 13:45:30 thallarch network[18470]: Failed to bring the network up for profile 'wlp4s0-limbo2'
Jun 14 13:45:30 thallarch systemd[1]: netctl@wlp4s0\x2dlimbo2.service: main process exited, code=exited, status=1/FAILURE
Jun 14 13:45:30 thallarch systemd[1]: Failed to start Networking for netctl profile wlp4s0-limbo2.
-- Subject: Unit netctl@wlp4s0\x2dlimbo2.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit netctl@wlp4s0\x2dlimbo2.service has failed.
-- 
-- The result is failed.
Jun 14 13:45:30 thallarch systemd[1]: Unit netctl@wlp4s0\x2dlimbo2.service entered failed state.
Jun 14 13:45:30 thallarch sudo[18463]: pam_unix(sudo:session): session closed for user root

I have tried both with the obfuscated password using wpa_passphrase and the one in clear text.
I should also mention that i have no problem connecting to my WPA2 Personal 2.4ghz wireless TKIP (only) network.

Offline

#2 2013-06-16 04:36:10

oboenerd
Member
From: Right behind you.
Registered: 2012-08-15
Posts: 52

Re: netctl and WPA2 Personal AES, problem with authentication

Can you try using wpa_supplicant to connect?  You may get some clues from its output.

"I quoted myself." -oboenerd

Offline

#3 2013-06-19 11:34:07

thall
Member
Registered: 2012-05-30
Posts: 12

Re: netctl and WPA2 Personal AES, problem with authentication

Okey, I think Im on something here:

wpa_supplicant config

ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel # allow control for members in the 'wheel' group                                                                               
update_config=1
ap_scan=1
 
network={
  ssid="limbo"
  bssid=20:4E:7F:71:D0:04
  #psk="hidden"
  psk=8f3f...
}

This is the output from $> wpa_supplicant -B -D nl80211 -i wlp4s0 -c /etc/wpa_supplicant/limbo.conf -dd -f /tmp/dump_wpa_supplicant

wpa_supplicant v2.0                                                                      
Successfully initialized wpa_supplicant
Initializing interface 'wlp4s0' conf '/etc/wpa_supplicant/limbo.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/limbo.conf' -> '/etc/wpa_supplicant/limbo.conf'
Reading configuration file '/etc/wpa_supplicant/limbo.conf'
ctrl_interface='DIR=/run/wpa_supplicant GROUP=wheel'
update_config=1
ap_scan=1
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=5): 
     6c 69 6d 62 6f                                    limbo
BSSID - hexdump(len=6): 20 4e 7f 71 d0 04                  
PSK - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='limbo'
nl80211: interface wlp4s0 in phy phy0
rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0
rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=0
nl80211: Set mode ifindex 4 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x16d5a00
nl80211: Register frame type=0xd0 nl_handle=0x16d5a00
nl80211: Register frame match - hexdump(len=2): 04 0a
nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
nl80211: Register frame match - hexdump(len=2): 04 0a
nl80211: Failed to register Action frame processing - ignore for now
netlink: Operstate: linkmode=1, operstate=5
nl80211: driver param='(null)'
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz
nl80211: 2457-2482 @ 40 MHz 
nl80211: 2474-2494 @ 20 MHz 
nl80211: 5170-5250 @ 40 MHz 
nl80211: 5735-5835 @ 40 MHz 
nl80211: 57240-63720 @ 2160 MHz
nl80211: Added 802.11b mode based on 802.11g information
wlp4s0: Own MAC address: 00:26:08:dc:85:72
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=4 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wlp4s0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlp4s0: Setting scan request: 0 sec 100000 usec
WPS: Set UUID for interface wlp4s0
WPS: UUID based on MAC address - hexdump(len=16): 58 5f f7 31 b2 76 5d 30 bc 67 4d c1 25 d8 31 33 
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=10 (from group name 'wheel')
wlp4s0: Added interface wlp4s0                                                           
wlp4s0: State: DISCONNECTED -> DISCONNECTED
wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Daemonize..
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlp4s0' added
nl80211: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlp4s0' added
nl80211: if_removed already cleared - ignore event
wlp4s0: State: DISCONNECTED -> SCANNING
wlp4s0: Starting AP scan for wildcard SSID
nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
Scan requested (ret=0) - scan timeout 10 seconds
nl80211: Event message available
nl80211: Scan trigger
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlp4s0' added
nl80211: if_removed already cleared - ignore event
nl80211: Event message available
nl80211: New scan results available
wlp4s0: Event SCAN_RESULTS (3) received
nl80211: Received scan results (21 BSSes)
wlp4s0: BSS: Start scan result update 1
wlp4s0: BSS: Add new id 0 BSSID 20:4e:7f:71:d0:02 SSID 'GET_OFF_MY_LAN'
wlp4s0: BSS: Add new id 1 BSSID 00:1f:33:fa:68:01 SSID 'NETGEAR'
wlp4s0: BSS: Add new id 2 BSSID 20:4e:7f:71:d0:04 SSID 'limbo'
wlp4s0: BSS: Add new id 3 BSSID 74:44:01:72:6f:fa SSID 'ohyran'
wlp4s0: BSS: Add new id 4 BSSID b8:a3:86:a4:6f:c2 SSID 'Kjansson'
wlp4s0: BSS: Add new id 5 BSSID 00:19:5b:00:f9:41 SSID 'Routary'
wlp4s0: BSS: Add new id 6 BSSID 34:21:09:02:61:88 SSID 'AirLink29150'
wlp4s0: BSS: Add new id 7 BSSID 14:d6:4d:cd:56:ac SSID 'dlink'
wlp4s0: BSS: Add new id 8 BSSID 00:1f:33:28:86:2a SSID 'NETGEAR-2.4-G'
wlp4s0: BSS: Add new id 9 BSSID 00:27:19:80:ee:6c SSID 'PP-LINK'
wlp4s0: BSS: Add new id 10 BSSID 00:24:b2:59:5d:af SSID 'Sofia-dator-Wireless'
wlp4s0: BSS: Add new id 11 BSSID 00:24:fe:00:83:47 SSID 'schrem'
wlp4s0: BSS: Add new id 12 BSSID 00:24:01:8f:e5:1e SSID '504'
wlp4s0: BSS: Add new id 13 BSSID 08:76:ff:83:42:94 SSID 'TeliaGateway08-76-FF-83-42-94'
wlp4s0: BSS: Add new id 14 BSSID 58:98:35:7f:08:7d SSID 'Bettan'
wlp4s0: BSS: Add new id 15 BSSID 58:98:35:bb:3b:57 SSID 'TeliaGateway58-98-35-BB-3B-57'
wlp4s0: BSS: Add new id 16 BSSID 00:1f:33:fa:70:03 SSID 'Skatteverket'
wlp4s0: BSS: Add new id 17 BSSID 84:1b:5e:da:0a:4a SSID 'NETGEAR14'
wlp4s0: BSS: Add new id 18 BSSID 4c:60:de:74:05:20 SSID '3Bredband0520'
wlp4s0: BSS: Add new id 19 BSSID 00:26:44:99:57:0f SSID 'TeliaGateway00-26-44-99-57-0F'
wlp4s0: BSS: Add new id 20 BSSID 00:18:4d:8a:cc:66 SSID 'router'
BSS: last_scan_res_used=21/32 last_scan_full=0
wlp4s0: New scan results available
WPS: Unknown Vendor Extension (Vendor ID 9442)
WPS: Unknown Vendor Extension (Vendor ID 9442)
WPS: Unknown Vendor Extension (Vendor ID 9442)
WPS: AP 00:1f:33:fa:68:01 type 0 added
WPS: Unknown Vendor Extension (Vendor ID 9442)
WPS: AP 74:44:01:72:6f:fa type 0 added
WPS: AP b8:a3:86:a4:6f:c2 type 0 added
WPS: AP 34:21:09:02:61:88 type 0 added
WPS: AP 14:d6:4d:cd:56:ac type 0 added
WPS: AP 00:1f:33:28:86:2a type 0 added                                                   
WPS: AP 00:24:b2:59:5d:af type 0 added
WPS: AP 00:24:fe:00:83:47 type 0 added
WPS: AP 00:1f:33:fa:70:03 type 0 added
WPS: AP 84:1b:5e:da:0a:4a type 0 added
WPS: AP 4c:60:de:74:05:20 type 0 added
WPS: AP[0] 00:1f:33:fa:68:01 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[1] 74:44:01:72:6f:fa type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[2] b8:a3:86:a4:6f:c2 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[3] 34:21:09:02:61:88 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[4] 14:d6:4d:cd:56:ac type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[5] 00:1f:33:28:86:2a type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[6] 00:24:b2:59:5d:af type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[7] 00:24:fe:00:83:47 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[8] 00:1f:33:fa:70:03 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[9] 84:1b:5e:da:0a:4a type=0 tries=0 last_attempt=-1 sec ago blacklist=0
WPS: AP[10] 4c:60:de:74:05:20 type=0 tries=0 last_attempt=-1 sec ago blacklist=0
wlp4s0: Selecting BSS from priority group 0
wlp4s0: 0: 20:4e:7f:71:d0:02 ssid='GET_OFF_MY_LAN' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-29
wlp4s0:    skip - SSID mismatch
wlp4s0: 1: 00:1f:33:fa:68:01 ssid='NETGEAR' wpa_ie_len=0 rsn_ie_len=20 caps=0x531 level=-29 wps
wlp4s0:    skip - SSID mismatch
wlp4s0: 2: 20:4e:7f:71:d0:04 ssid='limbo' wpa_ie_len=0 rsn_ie_len=24 caps=0x11 level=-37
wlp4s0:    selected based on RSN IE
wlp4s0:    hardware does not support HT PHY
wlp4s0:    skip - rate sets do not match
....
....

limbo is the network i try to connect to, but it says it doesnt support HT PHY which has to do with 5GHz network? So it seems like it not using the correct drivers? The broadcom-wl drivers are installed and loaded into the kernel.

wpa_supplincant only shows me three available drivers: wext, nl80211, wired. Shouldnt it be possible to select the broadcom drivers?

Offline

#4 2013-06-19 11:58:54

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,489

Re: netctl and WPA2 Personal AES, problem with authentication

No, in lsmod you should see the broadcom-wl being used by the netlink. You could try again without specifying any driver.
An alternative: move your "limbo" profile, execute "wifi-menu" (part of netctl) and compare the profile it generates to yours.

Offline

#5 2013-06-26 08:59:37

thall
Member
Registered: 2012-05-30
Posts: 12

Re: netctl and WPA2 Personal AES, problem with authentication

Strike0 wrote:

No, in lsmod you should see the broadcom-wl being used by the netlink. You could try again without specifying any driver.
An alternative: move your "limbo" profile, execute "wifi-menu" (part of netctl) and compare the profile it generates to yours.

Nice, wpa_supplicant connected if the driver specification was left out.
$> sudo wpa_supplicant -i wlp4s0 -f /tmp/wpa_supplicant -c /etc/wpa_supplicant/limbo.conf -B

Successfully initialized wpa_supplicant                                                  
wlp4s0: Trying to associate with 20:4e:7f:71:d0:04 (SSID='limbo' freq=5180 MHz)
wlp4s0: Association request to the driver failed
wlp4s0: Associated with 20:4e:7f:71:d0:04
wlp4s0: WPA: Key negotiation completed with 20:4e:7f:71:d0:04 [PTK=CCMP GTK=TKIP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to 20:4e:7f:71:d0:04 completed [id=0 id_str=]

And this is my wpa_supplicant config /etc/wpa_supplicant/limbo.conf

ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel # allow control for members in the 'wheel' group                                                                               
update_config=1
ap_scan=1
 
network={
  ssid="limbo"
  bssid=20:4E:7F:71:D0:04
  psk=8f3fa...
}

However, I still cant connect to it via netctl using this config /etc/netctl/wlp4s0-limbo (Generated by wifi-menu)

Description='Automatically generated profile by wifi-menu'                               
Interface=wlp4s0
Connection=wireless
Security=wpa
ESSID=limbo
IP=dhcp
Key=8f3fa...

Yields the error message
$> journalctl -xn

-- Logs begin at Mon 2001-01-01 01:02:40 CET, end at Wed 2013-06-26 10:51:10 CEST. --
Jun 26 10:50:54 thallarch sudo[2775]: thall : TTY=pts/0 ; PWD=/home/thall ; USER=root ; COMMAND=/usr/bin/netctl start wlp4s0-limbo
Jun 26 10:50:54 thallarch sudo[2775]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 26 10:50:54 thallarch systemd[1]: Starting Networking for netctl profile wlp4s0-limbo...
-- Subject: Unit netctl@wlp4s0\x2dlimbo.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--                                                                                       
-- Unit netctl@wlp4s0\x2dlimbo.service has begun starting up.
Jun 26 10:50:54 thallarch network[2782]: Starting network profile 'wlp4s0-limbo'...
Jun 26 10:51:10 thallarch network[2782]: WPA association/authentication failed for interface 'wlp4s0'
Jun 26 10:51:10 thallarch network[2782]: Failed to bring the network up for profile 'wlp4s0-limbo'
Jun 26 10:51:10 thallarch systemd[1]: netctl@wlp4s0\x2dlimbo.service: main process exited, code=exited, status=1/FAILURE
Jun 26 10:51:10 thallarch systemd[1]: Failed to start Networking for netctl profile wlp4s0-limbo.
-- Subject: Unit netctl@wlp4s0\x2dlimbo.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit netctl@wlp4s0\x2dlimbo.service has failed.
--
-- The result is failed.
Jun 26 10:51:10 thallarch systemd[1]: Unit netctl@wlp4s0\x2dlimbo.service entered failed state.
Jun 26 10:51:10 thallarch sudo[2775]: pam_unix(sudo:session): session closed for user root

I cant see any major different that shouldnt make netctl unable to connect to my network? Is there anything special needed in the netctl config for wpa2 aes psk 5ghz network?

Offline

#6 2013-06-26 09:27:09

thall
Member
Registered: 2012-05-30
Posts: 12

Re: netctl and WPA2 Personal AES, problem with authentication

I also tried to include the wpa_supplicant config

Description='Automatically generated profile by wifi-menu'                               
Interface=wlp4s0                                 
Connection=wireless                              
Security=wpa-config                              
WPAConfigFile='/etc/wpa_supplicant/limbo.conf'

which yields the same result hmm

Offline

#7 2013-10-18 21:51:34

leha2000
Member
Registered: 2013-10-18
Posts: 4

Re: netctl and WPA2 Personal AES, problem with authentication

Hello all.
After update netctl wireless_wpa-static profile was broken.
If I using wpa_supplicant for connection, I have success.
The  cause of this is next feature:
When I launch wpa_supplicant I using WEXT driver.

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

When I calling netctl, the netctl using cfg80211 driver:

dom ~ # LC_ALL=C journalctl -xn
-- Logs begin at Mon 2013-05-06 04:42:54 MSK, end at Sat 2013-10-19 01:56:13 MS
Oct 19 01:55:48 dom kernel: wlan0: deauthenticating from 1c:7e:e5:0c:c5:db by l
Oct 19 01:55:48 dom kernel: cfg80211: Calling CRDA to update world regulatory d
Oct 19 01:55:55 dom systemd[1]: Starting Networking for netctl profile dom...
-- Subject: Unit netctl@dom.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@dom.service has begun starting up.
Oct 19 01:55:55 dom network[3036]: Starting network profile 'dom'...
Oct 19 01:55:56 dom kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 19 01:56:13 dom network[3036]: WPA association/authentication failed for in
Oct 19 01:56:13 dom network[3036]: Failed to bring the network up for profile '
Oct 19 01:56:13 dom systemd[1]: netctl@dom.service: main process exited, code=e
Oct 19 01:56:13 dom systemd[1]: Failed to start Networking for netctl profile d
-- Subject: Unit netctl@dom.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02
-- 
-- Unit netctl@dom.service has failed.

How to use WEXT driver with netctl force?

Offline

#8 2013-10-19 17:37:12

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,489

Re: netctl and WPA2 Personal AES, problem with authentication

Welcome to the bbs, leha2000. You can specify the driver with 

WPADriver=

have a look for it in 

man netctl.profile

Offline

#9 2013-11-08 01:40:25

leha2000
Member
Registered: 2013-10-18
Posts: 4

Re: netctl and WPA2 Personal AES, problem with authentication

A big thanks. Thats good smile

Offline

Pages: 1

Board footer

Powered by FluxBB