Enh_sec

Patrick Poncet patrick at poncet.ca
Mon May 31 21:14:28 EDT 2004


I managed to get a simple wpa setup going:

WiredLan----hostapd Master (wds) ((((((((((    ))))))))))  hostap driver
Managed wds---WiredLan


I was trying to reduce visibility in an effort to increase security, by
enabling enh_sec = 3.


It seems to confuse wpa_supplicant.   My wpa_supplicant config is:


Network={
	scan_ssid=1
	ssid="tidsppg"
	bssid=11:22:33:44:55:66
	proto=WPA
	key-mgmt=WPA-PSK
	pairwise=TKIP CCMP
	group=TKIP CCMP
	
psk=0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
}




wpa_supplicant does indeed a scan and discovers my AP.  But here's the
output


...
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=7)
     74 69 64 73 70 70 67                              tidsppg
Wireless event: cmd=0x8b19 len=12
Received 230 bytes of scan results (1BSSes)
Scan results: 1
0: 11:22:33:44:55:66 ssid='' wpa_ie_len=28 rsn_ie_len=0
No suitable AP found.
...


It looks like it gives up because ssid = ''.  ssid='' is indeed
expected... But shouldn't wpa_supplicant continue anyway?



Let me know when you think

Thanks,
Patrick




More information about the HostAP mailing list