Re: wpa_supplicant options
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. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
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. 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 NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Joel Goguen http://jgoguen.net/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
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 NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
Will the options be exposed in a config file later on? Having them hard-coded doesn't allow users much choice if they have even the slightest need to configure wpa_supplicant. On 9/4/07, Tambet Ingo [EMAIL PROTECTED] wrote: On 9/4/07, Joel Goguen [EMAIL PROTECTED] 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. I've tried /etc/wpa_supplicant/functions.sh, /etc/wpa_supplicant/ifupdown.sh, and /etc/NetworkManager/dispatcher.d/01ifupdown so far, but I don't see what other files would be used. Can someone please point me to how to change the wpa_supplicant options NetworkManager uses? It's hard-coded in the source, for 0.6 branch, see src/nm-device-802-11-wireless.c (supplicant_interface_init). Tambet -- Joel Goguen http://jgoguen.net/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
On 9/4/07, Joel Goguen [EMAIL PROTECTED] wrote: Will the options be exposed in a config file later on? Having them hard-coded doesn't allow users much choice if they have even the slightest need to configure wpa_supplicant. In short, no. It's not about users' choice, it's about policy to not support broken wireless drivers that do not (correctly) implement wireless extensions. Some distros (opensuse) have different policies and patch NM to use madwifi wpa_supplicant driver. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: wpa_supplicant options
On Tue, 2007-09-04 at 17:19 +0300, Tambet Ingo wrote: On 9/4/07, Joel Goguen [EMAIL PROTECTED] wrote: Will the options be exposed in a config file later on? Having them hard-coded doesn't allow users much choice if they have even the slightest need to configure wpa_supplicant. In short, no. It's not about users' choice, it's about policy to not support broken wireless drivers that do not (correctly) implement wireless extensions. Some distros (opensuse) have different policies and patch NM to use madwifi wpa_supplicant driver. NM upstream will never use another driver than wext. Distros can (and some do) what they want. Drivers have _GOT_ to be fixed, and this default policy of NetworkManager has already fixed at least 3 drivers to support WEXT, which all drivers should be doing in the first place. If you have to rely on a different wpa_supplicant driver, then the kernel driver for your card is BUSTED. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
