On Mon, Mar 31, 2008 at 4:40 PM, Chatre, Reinette <reinette.chatre@xxxxxxxxx> wrote: > On Sunday, March 30, 2008 7:35 PM, John Goulah wrote: > > > Let me know where to go from here; if you still want the > > wpa_supplicant info I can post a bug for that, but the more major > > problem seems that I have to explicitly tell iwconfig what my AP mac > > address is, it wont associate otherwise even though "iwlist scan" > > turns it up just fine, but I'm not having much luck producing useful > > info here. > > It is not clear how you are associating. Are you using wpa_supplicant or > iwconfig? Please submit a bug with the details of your setup and steps > to associate. Please include the wpa_supplicant logs and the driver > logs. > I have to use both. I have to use iwconfig to pick my essid and access point, and I use wpa_supplicant to setup the encryption tunnel. Then I dhclient the IP address. In previous wireless experience, once I've set the essid , it automatically associates to the access point (at least I can see that the MAC address is defined when I run iwconfig). That does not happen with this driver- only "Not Associated" or "Invalid". Unfortunately debug for these cases isn't spitting any info. I've been setting my access point mac address specifically with "iwconfig wlan0 ap <MAC>" -before- running wpa_supplicant since I thought I had to be associated before running wpa_supplicant but it sounds like you are saying otherwise, so I'll try that tonight and then submit my findings in a bug. If something I've said sounds completely wrong let me know. Thanks, John -- 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
