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
