On Fri, Dec 03, 2010 at 10:49:55PM +0000, Dave Kilroy wrote: > >> >> But after removing the line: ap_scan=2 > >> >> the association fails. > >> >> The log is in the second attachment. > >> >> > >> >> Also I have included in the 3rd attachement wpa_supplicant.log when > >> >> NetworkManager is used. > >> > >> > The failure and NM case are the same. There is still a problem with > >> > scanning. wpa_supplicant initiates a scan, and it appears to time out. > >> > Without scan results wpa_supplicant is not able to select an > >> > appropriate AP. > >> > > >> > Is the driver reporting any scanning issues in dmesg while > >> > wpa_supplicant is running? > > > > In dmesg there is: > > ADDRCONF(NETDEV_UP): eth1: link is not ready > > > > and on standard error: > > ioctl[SIOCSIWENCODEEXT]: Invalid argument > > Those are expected. > > I'm at a loss. I've looked at the wpa_supplicant code, and had another > look at the driver. The scan should be a plain wildcard scan - which > you've identified works. > > Does setting scan_ssid=1 in the wpa_supplicant network block change > the behaviour? That's usually only necessary for hidden SSIDs - but > I'd like to know if the scan succeeds in this case. No It doesn't work. But I have more informations for you. I have been testing different versions of wpa_supplicant and I have found that if a use wpa_supplicant 0.7.0 or earlier, it works. With 0.7.1 or newer it fails. wpa_supplicant 0.7.0 works even without applying your patch. I hope this helps. Giacomo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
