Thanks for the heads up. This explains issues I was having with an NDIS-only card.
James On Sep 24, 2007, at 10:52 PM, Mikore.Li at Sun.COM wrote: > WPA is not enabled in current NDISwrapper/bcmndis. To enable it, we > need > to import some codes from Freebsd/NDIS, since it was said freebsd/NDIS > can now support WPA. > > - Michael > > steve trabert wrote: >> I am having trouble connecting to my AP with SXDE09/07. I have >> used ndis to create a driver, and it has successfully attached. >> nwam comes up and sees the AP but thinks it is using wep. Here is >> what dladm -scan-wifi says: >> >> LINK ESSID BSSID/IBSSID SEC STRENGTH >> MODE SPEED >> bcmndis0 1iRvNQT2gEba8UkF xx:xx:xx:xx:xx:xx wep very >> good g 22Mb >> >> If I try to connect to this ESSID with nwam it asks for the key, I >> give it the WPA key, and it silently fails. /var/adm/messages shows: >> >> Sep 24 16:36:26 C128189 nwamd[27]: [ID 437268 daemon.error] >> key_string_to_secobj_value: invalid WEP key length >> Sep 24 16:36:26 C128189 nwamd[27]: [ID 938369 daemon.error] >> get_user_key: failed to store user-specified key >> Sep 24 16:36:30 C128189 nwamd[27]: [ID 437268 daemon.error] >> key_string_to_secobj_value: invalid WEP key length >> Sep 24 16:36:30 C128189 nwamd[27]: [ID 938369 daemon.error] >> get_user_key: failed to store user-specified key >> Sep 24 16:36:30 C128189 nwamd[27]: [ID 524068 daemon.warning] >> Could not connect to chosen WLAN 1iRvNQT2gEba8UkF; going to auto-conf >> >> On the other hand, if I tell nwam OTHER, and then say WPA, and >> then supply the WPA key it silently fails and /var/adm/messages >> shows: >> >> Sep 24 16:38:48 C128189 nwamd[27]: [ID 638921 daemon.error] >> retrieve_key: could not get key from secure object >> 'nwam-1iRvNQT2gEba8UkF': buffer size too small >> Sep 24 16:38:59 C128189 nwamd[27]: [ID 487253 daemon.error] >> store_key: could not create secure object 'nwam-1iRvNQT2gEba8UkF' >> for key: object already exists >> Sep 24 16:38:59 C128189 nwamd[27]: [ID 938369 daemon.error] >> get_user_key: failed to store user-specified key >> Sep 24 16:39:00 C128189 nwamd[27]: [ID 638921 daemon.error] >> retrieve_key: could not get key from secure object >> 'nwam-1iRvNQT2gEba8UkF': buffer size too small >> Sep 24 16:39:03 C128189 nwamd[27]: [ID 487253 daemon.error] >> store_key: could not create secure object 'nwam-1iRvNQT2gEba8UkF' >> for key: object already exists >> Sep 24 16:39:03 C128189 nwamd[27]: [ID 938369 daemon.error] >> get_user_key: failed to store user-specified key >> Sep 24 16:39:03 C128189 nwamd[27]: [ID 524068 daemon.warning] >> Could not connect to chosen WLAN 1iRvNQT2gEba8UkF; going to auto-conf >> >> In another OS, which I am using to communicate with the forum >> through the same AP, the wireless network key panel shows >> Network Authentication: WPA-PSK >> Data encryption: TKIP >> Network key: ******** >> >> AP is actiontec gt701-wg with qwest firmware QW05.5. >> >> wireless device is Dell wireless 1450 Dual ABand WLAN Mini-PCI >> Card. Driver version is 3.120.27.0 under Solaris and the other >> OS. Ndis wrapper tookit version is 1.1. >> >> My guess is that in solaris is incorrectly deciding the AP is >> using wep and subsequently tries to communicate using wep >> security. Even when I tell nwam to use WPA security it has the >> above key length problems making me think it is trying to use >> wep. In the other OS I tell it to use WPA-PSK and TKIP, and it >> works. >> >> Can anyone confirm this hypothesis or tell me how to confirm it? >> >> Is there a way to force the protocal to WPA-PSK / TKIP? >> >> Thanks for any insight. >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> laptop-discuss mailing list >> laptop-discuss at opensolaris.org >> > _______________________________________________ > laptop-discuss mailing list > laptop-discuss at opensolaris.org
