On Wed, 2007-09-05 at 08:43 -0300, Joel Goguen wrote: > It's working great everywhere, except at my university. They just > implemented a WPA2 secured network, using TTLS/PAP, and NetworkManager > appears to hang after completing "Stage 2 of 5". I say "appears" > because it functions normally, the list of wireless networks updates, > and after a few minutes it asks me for the authentication information > again and then times out. If I disable NetworkManager and bring up > wpa_supplicant and the interface manually with -Dwext then I get the > same thing. If I use -Dmadwifi, then it all works almost immediately.
So if you can reproduce the issue without NetworkManager in the mix, that helps narrow down the problem. This definitely seems like a driver problem to me. If you provide the wpa_supplicant config files to the madwifi driver people, likely they will be able to help you debug why their WEXT support isn't working here. The atheros situation will hopefully get a lot better in a few kernel versions because the ar5k mac80211-based driver will be upstream. And it'll have the same WEXT problems that iwlwifi and bcm43xx and all the others do. Which means it'll likely work quite a lot better than madwifi. Dan > I added a quick check to NetworkManager for the existence of a file, > and if it exists to pass 'madwifi' to wpa_cli instead of 'wext', and > after recompiling, installing, and creating that file, NetworkManager > authenticates to this network almost immediately. It's a horrible > hack job, if I'd wanted to spend more than 5 minutes I should have > added a command-line option or read a config file... > > On 9/5/07, Simon Geard <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-09-04 at 08:42 -0300, Joel Goguen wrote: > > > I'm trying to force NetworkManager to run wpa_supplicant with a > > > specific set of options (most importantly, -Dmadwifi) but it seems no > > > matter what files I edit, it always gets run with the same options. > > > > Why do you need to use -Dmadwifi? For a long time now, the madwifi > > drivers have provided sufficient support for wireless extensions that > > the default (-Dwext) ought to be fine. It's worked fine for me since at > > least last year some time... > > > > Simon. > > > > _______________________________________________ > > NetworkManager-list mailing list > > [email protected] > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > > > _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
