madwifi wpa and wpa_supplicant not recognizing AP

Jouni Malinen jkmaline at cc.hut.fi
Fri Jun 25 00:13:55 EDT 2004


On Thu, Jun 24, 2004 at 10:42:14AM +0200, Thomas Hänig wrote:

> thomas-nbk:/home/thomas # wpa_supplicant -i ath1 -c /etc/wpa_supplicant.conf 
> -dd

> l2_packet_receive - recv: Network is down

You will eventually need to set the interface up for the authentication
to succeed..

> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=10):
>      74 6f 70 5f 73 65 63 72 65 74                     top_secret      
> Wireless event: cmd=0x8b19 len=12
> Received 274 bytes of scan results (1 BSSes)
> Scan results: 1
> 0: 00:20:a6:4d:35:6d ssid='' wpa_ie_len=26 rsn_ie_len=0
>    skip - SSID mismatch
> No suitable AP found.

> The ssid='' is correct because the AP is not broadcasting it, and "top_secret" 
> is the real name.Somehow it should match. How?

wpa_supplicant expects that the driver updates the SSID information
based on the Probe Response frames in case the AP is hiding the SSID
from Beacon frames. I have not tested this with madwifi, so I'm not sure
whether it is reporting the SSIDs from Probe Responses. Based on madwifi
CVS log entries from today, it looks like Sam just fixed something that
was related to this. I don't know whether this fixes the case you saw,
but it might be worthwhile testing the latest CVS snapshot of the
driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the HostAP mailing list