| View previous topic :: View next topic |
| Author |
Message |
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
 Posted: Sun Dec 27, 2015 9:23 pm Post subject: [SOLVED]wpa_supplicant notconnecting to my wireless NW |
 |
|
[edit] all because of a typo on my part !!
Im a bit new to all this
im trying to configure my wireless NW - not got as far as a GUI yet
| Quote: | mars / # wpa_cli
wpa_cli v2.4
Copyright (c) 2004-2015, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Interactive mode
Could not connect to wpa_supplicant: (nil) - re-trying |
| Quote: | mars / # cat /etc/conf.d/net
config_eth0="dhcp"
modules_wlan0="wpa_supplicant"
wpa_supplicant_wlan0="-Dnl80211 -d -f /var/log/wpa_supplicant.log"
config_wlan0="dhcp"
mars / #
mars / # cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
#ap_scan=0
#update_config=1
network={
ssid="BTHub4-xxxx"
psk="1234567890"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
group=CCMP TKIP
pairwise=CCMP TKIP
priority=5
}
|
iI think it is seeing the network but not connecting to it
| Quote: | wpa_supplicant -Dnl80211 -iwlan0 -C/var/run/wpa_supplicant/ -c/etc/wpa_supplicant/wpa_supplicant.conf -dd
<snipped>
wlan0: New scan results available (own=1 ext=0)
wlan0: Radio work 'scan'@0x173ec90 done in 5.555574 seconds
wlan0: Selecting BSS from priority group 5
wlan0: 0: 2c:39:96:b6:fb:8b ssid='BTWifi-X' wpa_ie_len=26 rsn_ie_len=24 caps=0x431 level=-49
wlan0: skip - SSID mismatch
wlan0: 1: 2c:39:96:b6:fb:86 ssid='BTHub4-xxxx' wpa_ie_len=26 rsn_ie_len=24 caps=0x431 level=-51 wps
wlan0: skip - SSID mismatch
wlan0: 2: e0:ca:94:bb:ff:66 ssid='P2PJANE-PC' wpa_ie_len=0 rsn_ie_len=20 caps=0x511 level=-73
wlan0: skip - SSID mismatch
wlan0: 3: 2c:39:96:b6:fb:89 ssid='BTWifi-with-FON' wpa_ie_len=0 rsn_ie_len=0 caps=0x421 level=-49
wlan0: skip - SSID mismatch
wlan0: No suitable network found |
?
Last edited by orkneywool on Sun Jan 03, 2016 2:26 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54810
Location: 56N 3W
|
| Posted: Sun Dec 27, 2015 11:39 pm Post subject: |
|
|
orkneywool,
Your SSID is case sensitive and there are a few illegal characters for SSID too.
It claims it can't match your SSID.
A problem waiting to happen is
With the quotes, its a string that will be applied to the string to hex converter before its used for your key.
Without the quotes, its treated an a hex number to be used directly.
Both psk="1234567890" and psk=1234567890 are correct syntax but they are different keys.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
| Posted: Mon Dec 28, 2015 5:35 pm Post subject: |
|
|
here my wpa_supplicant.conf
| Quote: | ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
#ap_scan=0
#update_config=1
network={
ssid="BTHub4-SRJS"
psk=86abcfe876
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
group=CCMP TKIP
pairwise=CCMP TKIP
priority=5
}
|
and the output from the command line
| Quote: |
wpa_supplicant -B -iwlp1s6 -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext
Successfully initialized wpa_supplicant
Line 7: Invalid PSK '86abcfe876'.
Line 7: failed to parse psk '86abcfe876'.
Line 14: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.
|
|
|
| Back to top |
|
|
quilosaq
Veteran
Joined: 22 Dec 2009
Posts: 1559
|
| Posted: Mon Dec 28, 2015 8:27 pm Post subject: |
|
|
| Quote: | | Line 7: Invalid PSK '86abcfe876'. |
A valid psk key needs 64 hexa digits or a string (double quoted) from 8 to 63 ASCII characters. Your current key is only 10 hexa characters. |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Mon Dec 28, 2015 8:33 pm Post subject: |
|
|
| orkneywool wrote: | | Code: | Line 7: Invalid PSK '86abcfe876'.
Line 7: failed to parse psk '86abcfe876'.
Line 14: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'. |
|
orkneywool ... how did you aquire/generate the psk? The above isn't a 'psk', its a "word".
| wpa_passphrase BTHub4-SRJS 86abcfe876: | network={
ssid="BTHub4-SRJS"
#psk="86abcfe876"
psk=f49a99ab6a6e14e93573f0cb7bab08845684468b0c19cf26adfa54ab347e212e
} |
As for your initial "SSID mismatch", this could be caused by a number of things, most likely another 'VAP' (virtual AP) with the same SSID. You could supply the BSSID which hopefully will avoid the issue:
| Code: | network={
ssid="BTHub4-SRJS"
bssid=2C:39:96:B6:FB:86
psk=f49a99ab6a6e14e93573f0cb7bab08845684468b0c19cf26adfa54ab347e212e
scan_ssid=0
} |
If the above fails then please supply (via pastebin) the full wpa_supplicant.log, and the output of
| Code: | | # awk '{RS="Cell"}/BTHub4-SRJS/' <(iwlist dev wlp1s6 scan) |
Also, note in the above you've provided '-iwlan0' and '-iwlp1s6', and used '-Dnl80211' and '-Dwext' ... that can't be right, at least for the interface name, so consistancy. Your interface probably is 'wlp1s6', and should be using '-Dnl80211'.
best ... khay |
|
| Back to top |
|
|
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54810
Location: 56N 3W
|
| Posted: Tue Dec 29, 2015 4:20 pm Post subject: |
|
|
orkneywool,
psk=86abcfe876 is a hex number, to be used as the psk directly.
psk="86abcfe876" is a text string to be converted to hex before its used as the key.
The quotes matter. If your Access Point uses a pass phrase, use the same pass phrase here - in quotes.
If it uses a hex key, most don't, use it here but no quotes.
Its double quotes.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
| Posted: Wed Dec 30, 2015 8:53 pm Post subject: |
|
|
| Quote: | | awk '{RS="Cell"}/BTHub4-SRJS/' <(iwlist dev wlp1s6 scan) |
says iwlist unknown command 'wlp1s6
the relevant ( i think) output of iwlist wlp1s6 scan is here http://pastebin.com/a33MLaUM
the BT Home hubs come with a 10digit key , not a passphrase
ive generated a wpa_supplicant.conf file with wpa_passphrase
the attempt at connection is here
http://pastebin.com/9T28581g
ive used genkernel if its relevant
the output of lspci -k is
| Quote: | 01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller
Kernel driver in use: rtl818x_pci |
|
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Wed Dec 30, 2015 9:51 pm Post subject: |
|
|
| orkneywool wrote: | | the BT Home hubs come with a 10digit key, not a passphrase |
orkneywool ... that sounds like a wep key (generally 10 digit), or WPS key (though wps is eight digit, not ten). Anyhow, from the scan I can't tell if wps is in use (as iwlist doesn't show extended capabilities), and wep doesn't seem to be available.
| orkneywool wrote: | | [...] the attempt at connection is here |
That shows 'ap_scan=0' ... which shouldn't be the case (as that is for 802.11x for wired networks) ... I suspect that is why we see "could not read SSID from driver" subsequently.
Besides the psk the following should be correct:
| /etc/wpa_supplicant/wpa_supplicant.conf: | ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
update_config=1
ap_scan=1
network={
ssid="BTHub4-SRJS"
bssid=2C:39:96:B6:FB:86
scan_freq=2462
scan_ssid=0
proto=WPA2
auth_alg=OPEN
key_mgmt=WPA-PSK
group=TKIP
pairwise=CCMP
psk=
} |
If this fails then it should be due to authentication ... and we then know the psk provided is incorrect.
best ... khay |
|
| Back to top |
|
|
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54810
Location: 56N 3W
|
| Posted: Thu Dec 31, 2015 7:18 pm Post subject: |
|
|
orkneywool'
| Code: | Dec 31 17:18:24 mars kernel: [ 46.445578] wlan0: authenticate with 2c:39:96:b6:fb:86
Dec 31 17:18:24 mars kernel: [ 46.558580] wlan0: send auth to 2c:39:96:b6:fb:86 (try 1/3)
Dec 31 17:18:24 mars kernel: [ 46.560161] wlan0: authenticated
Dec 31 17:18:24 mars kernel: [ 46.562553] wlan0: associate with 2c:39:96:b6:fb:86 (try 1/3)
Dec 31 17:18:24 mars kernel: [ 46.564658] wlan0: RX AssocResp from 2c:39:96:b6:fb:86 (capab=0x431 status=0 aid=42)
Dec 31 17:18:24 mars kernel: [ 46.564691] wlan0: associated |
That's the hard bit done. With the wireless stuff out of the way, it can get an IP, if you ask it to.
Try Give it 20 sec or so and look in
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
orkneywool
n00b
Joined: 23 Dec 2015
Posts: 11
|
| Posted: Thu Dec 31, 2015 7:39 pm Post subject: |
|
|
sorry - my mistake
the gentoo log is
http://pastebin.com/LQGSM7ZD
the gentoo partition isnt connecting -the ubuntu one is |
|
| Back to top |
|
|
quilosaq
Veteran
Joined: 22 Dec 2009
Posts: 1559
|
| Posted: Thu Dec 31, 2015 8:01 pm Post subject: |
|
|
orkneywool,
The SSID of your AP is BTHub4-SJRS
and your wpa_supplicant.conf contains BTHub4-SRJS. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54810
Location: 56N 3W
|
| Posted: Thu Dec 31, 2015 8:06 pm Post subject: |
|
|
quilosaq,
Well caught!
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Networking & Security
