Help - Search - Members - Calendar
Full Version: Wpa-psk And 3.5.4
OESF Forums > General Forums > General Support and Discussion > Security and Networking
sojourner
Just flashed to Opie 3.5.4 using the 32-32 zImage on my collie and everything looks great with the exception of WPA-PSK CCMP on my Ambicom WL1100C.

I'm using the same wpa_supplicant.conf I used under 3.5.3 with no problems. I wrestled with it for a few hours and flashed back to 3.5.3 just to see if I missed something but after flashing and immediately starting up the wpa_supplicant in debug mode (hostap) it connected up with no issues. I did not need to make any changes under 3.5.3.

Flashed back to 3.5.4 and still no go. Disabling encryption works fine on 3.5.4 with this card but that isn't an option.

Any ideas out there? I've searched high and low to no avail.

Here is what i get from running "wpa_supplicant -Dhostap -iwlan0 -c/etc/wpa_supplicant.conf -dd":

CODE
Priority group 1
  id=0 ssid='lamessid'
wpa_driver_hostap_set_wpa: enabled=1
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_countermeasures: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=1

Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 233 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 1
0: 00:00:00:00:06:22 ssid='lamessid' wpa_ie_len=0 rsn_ie_len=0
  skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 233 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 1
0: 00:00:00:00:06:22 ssid='lamessid' wpa_ie_len=0 rsn_ie_len=0
  skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b19 len=12
Received 233 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 1
0: 00:00:00:00:06:22 ssid='lamessid' wpa_ie_len=0 rsn_ie_len=0
  skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
Signal 2 received - terminating
wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_hostap_set_wpa: enabled=0
wpa_driver_hostap_set_drop_unencrypted: enabled=0
wpa_driver_hostap_set_countermeasures: enabled=0


Same command and config works under 3.5.3

wpa_supplicant.conf looks like this:

CODE
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
network={
  ssid="lamessid"
  proto=WPA
  psk="somelamepassphrase"
  key_mgmt=WPA-PSK
  pairwise=CCMP
  group=CCMP
  priority=1
}


Regards,

-sojourner
sojourner
Looks like I'll have to go back to 3.5.3:

TuxMobil

The card no longer works with 3.5.4 sad.gif

I'd be willing to test changes to the hostap drivers in order to get this to work if any developers have time to mess with them.

-sojourner
nax
Hmm, it seems I'm not alone. I haven't 3.5.3 flashed before, so I didn't know thats problem of collie wpa support. I'm trying to get it working over the week. I'm try to use TKIP, evrithing seems to be set correctly but wpa_supplicant still returning:
CODE
Received 267 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 5
0: 00:11:d8:32:68:c7 ssid='nax.home' wpa_ie_len=0 rsn_ie_len=0
  skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec


But intresting is this:

CODE
root@znax:/etc# iwlist wlan0 scanning
wlan0     Scan completed :
         Cell 01 - Address: 00:11:D8:32:68:C7
                   ESSID:"nax.home"
                   Mode:Master
                   Frequency:2.432 GHz (Channel 5)
                   Quality:0/70  Signal level:-53 dBm  Noise level:-83 dBm
                   Encryption key:on
                   Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                             24 Mb/s; 36 Mb/s; 54 Mb/s
                   Extra:bcn_int=100
                   Extra:resp_rate=10
                   IE: WPA Version 1
                       Group Cipher : TKIP
                       Pairwise Ciphers (1) : TKIP
                       Authentication Suites (1) : PSK  
                   IE: IEEE 802.11i/WPA2 Version 1
                       Group Cipher : TKIP
                       Pairwise Ciphers (1) : TKIP
                       Authentication Suites (1) : PSK  


Paradox is, that wpa support was main thing why I flashed to 3.5.4 sad.gif
lardman
Have you submitted a bug or asked on the openzaurus mailing lists?

I know nothing about this subject, a bug or mailinglist question will get you far more exposure to the OZ devs.


Si
nax
Thanks for advice. Bug 819 submitted.

May be I'll try 3.5.3 too.
sojourner
QUOTE(lardman @ Apr 6 2006, 04:01 AM)
Have you submitted a bug or asked on the openzaurus mailing lists?

I know nothing about this subject, a bug or mailinglist question will get you far more exposure to the OZ devs.


Si
*


Thanks for the tip lardman, didn't even think of it.

nax: thanks for submitting the bug.

Best regards,

-sojourner
sojourner
Update.

Hrw has uploaded a new wpa_supplicant (wpa-supplicant_0.4.8-r1_arm.ipk) to the upgrades feed that resolves Bug #819.

Note that with the Ambicom WL1100C you will need to use -Dwext instead of -Dhostap when starting wpa_supplicant.

Kudos to Hrw for the speedy resolution.

-sojourner
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.