On Fri, Jan 15, 2010 at 04:51:33AM +0100, Peter Stuge <[email protected]> wrote: > > Should I include a section for the "linksys" (which has no encryption) > > AP as well? if yes, what should it look like? > > Yes, otherwise I don't think wpa_supplicant will do anything. > > network={ > ssid="linksys" > key_mgmt=NONE > } > > It could help to run it in foreground - you should see disconnect and > reauth then.
OK, when I add this, wpa_supplicant authenticates with the "wpa ap" on startup. That's fine, but when I do an "iwconfig eth0 essid linksys", the wpa_supplicant stdout is: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan. CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:1b:2f:51:25:70 (SSID='<wpa ap>' freq=2462 MHz) CTRL-EVENT-SCAN-RESULTS Associated with 00:1b:2f:51:25:70 WPA: Key negotiation completed with 00:1b:2f:51:25:70 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:1b:2f:51:25:70 completed (reauth) [id=0 id_str=] The dmesg diff is: --- a 2010-01-15 14:13:47.951510823 +0100 +++ b 2010-01-15 14:13:54.064510826 +0100 @@ -709,3 +709,11 @@ eth0: RX AssocResp from 00:1b:2f:51:25:70 (capab=0x431 status=0 aid=2) eth0: associated eth0: no IPv6 routers present +eth0: deauthenticating from 00:1b:2f:51:25:70 by local choice (reason=3) +eth0: direct probe to AP 00:1b:2f:51:25:70 (try 1) +eth0: direct probe responded +eth0: authenticate with AP 00:1b:2f:51:25:70 (try 1) +eth0: authenticated +eth0: associate with AP 00:1b:2f:51:25:70 (try 1) +eth0: RX AssocResp from 00:1b:2f:51:25:70 (capab=0x431 status=0 aid=2) +eth0: associated The MAC you see is the "wpa ap" one, so basically I can't switch to the linksys AP. (The MAC of the linksys AP - 00:12:17:D3:87:F5 - doesn't show up in either outputs.)
pgpOw8Coak4D3.pgp
Description: PGP signature
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
