On Monday, March 31, 2008 3:02 PM, John Goulah wrote: > 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. It should not be necessary to use both iwconfig and wpa_supplicant. wpa_supplicant will take care of the association for you. You will need to bring the interface up (ifconfig wlan0 up) before you run wpa_supplicant. If you run into issues, please also send wpa_supplicant's configuration and debug log. Thanks Reinette -- 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
