Hi Quaker,
I have done some more testing last evening, using my built-in Atheros adapter 
and a D-Link DWL-G730AP as router. The firmware in the router is upgraded to a 
version that does WPA2 in client mode (just for info).

> 
> You can run wpa_supplicant as a front-end program
> with debug information 
> by:|
> 
> # wpa_supplicant -i ath0 -F -dd
This shows a lot of messages in the console. wpa_supplicant seems to notice 
when the WiFi connection is broken and tries to reconnect automatically (e.g. 
when the router boots or when I switch the client adapter radio off and on 
again).
Sometimes I get MADWIFI_EVENT_SCAN_RESULTS messages every 1 sec and sometimes 
not.

WPA connection seems to go ok, as it always ends in the AUTHENTICATED state 
(though right after that it goes to IDLE state).
However, above that after the first disconnection, IP traffic seems to go to 
/dev/null. I could see some ETHER 888E ??? messages in snoop -d ath0 when WPA 
is connecting and the DHCPDISCOVER messages never get a response.

Then I tried to reset the router to non-authenticated mode and it worked 
normally, including DHCP and accessing the router admin interface through HTTP 
over the very WiFi connection.

Then I tried to set WPA auth in the router again and the client didn't get the 
IP address again.
Going through this cycle for some time, I noticed that when WPA is enabled the 
traffic gets lost between the WiFi and IP layers.
So I think there might be a problem with WPA support after all.
Could you give me any directions to try to gather more information and even 
debug it?

Could it be the same problem I am facing with the experimental cardbus driver, 
namely that I am having problems because of some incompatibility between 
Solaris 10 6/06 (which I am using) and the drivers (which are compatible with 
Solaris Express and OpenSolaris only)?

-- Douglas
 
 
This message posted from opensolaris.org

Reply via email to