[arch-projects] [netcfg] Getting rid of wireless_tools
Hello, wpa_supplicant is supposed to provide most of the wireless_tools functionality. I have set up a branch of netcfg that replaces all uses of wireless_tools by wpa_supplicant. http://projects.archlinux.org/users/remy/netcfg.git/log/?h=no-iwconfig iwconfig is still used by the deprecated IWCONFIG option, but there is still one thing I don't really understand. In src/connections/wireless, there is block that calls "iwconfig mode Managed" before starting wpa_supplicant. The log is not really explicit about why this was added (it merely says it was necessary for iwl3945), and wpa_supplicant man page only says it's necessary for the hostap driver, which we do not use. Does anybody knows the reason why it is needed? Rémy.
On Sun, Jun 19, 2011 at 11:13 AM, Rémy Oudompheng <remy@archlinux.org> wrote:
Hello,
wpa_supplicant is supposed to provide most of the wireless_tools functionality. I have set up a branch of netcfg that replaces all uses of wireless_tools by wpa_supplicant.
http://projects.archlinux.org/users/remy/netcfg.git/log/?h=no-iwconfig
iwconfig is still used by the deprecated IWCONFIG option, but there is still one thing I don't really understand.
In src/connections/wireless, there is block that calls "iwconfig mode Managed" before starting wpa_supplicant. The log is not really explicit about why this was added (it merely says it was necessary for iwl3945), and wpa_supplicant man page only says it's necessary for the hostap driver, which we do not use. Does anybody knows the reason why it is needed?
I think some drivers don't (didn't?) support switching modes if the interface is up, or something like that? -Dan
On 2011/6/19 Dan McGee <dpmcgee@gmail.com> wrote:
On Sun, Jun 19, 2011 at 11:13 AM, Rémy Oudompheng <remy@archlinux.org> wrote:
In src/connections/wireless, there is block that calls "iwconfig mode Managed" before starting wpa_supplicant. The log is not really explicit about why this was added (it merely says it was necessary for iwl3945), and wpa_supplicant man page only says it's necessary for the hostap driver, which we do not use. Does anybody knows the reason why it is needed?
I think some drivers don't (didn't?) support switching modes if the interface is up, or something like that?
So more precisely, the question is probably: is wpa_supplicant capable of manipulating interfaces that are down, just like iwconfig? Rémy.
On Sun, Jun 19, 2011 at 6:22 PM, Rémy Oudompheng <remyoudompheng@gmail.com> wrote:
On 2011/6/19 Dan McGee <dpmcgee@gmail.com> wrote:
On Sun, Jun 19, 2011 at 11:13 AM, Rémy Oudompheng <remy@archlinux.org> wrote:
In src/connections/wireless, there is block that calls "iwconfig mode Managed" before starting wpa_supplicant. The log is not really explicit about why this was added (it merely says it was necessary for iwl3945), and wpa_supplicant man page only says it's necessary for the hostap driver, which we do not use. Does anybody knows the reason why it is needed?
I think some drivers don't (didn't?) support switching modes if the interface is up, or something like that?
So more precisely, the question is probably: is wpa_supplicant capable of manipulating interfaces that are down, just like iwconfig?
I have an iwl3945, so I could help with testing. However, I'd need someone to tell me what setups to test and what problems to look for. -t
On 2011/6/19 Tom Gundersen <teg@jklm.no> wrote:
On Sun, Jun 19, 2011 at 6:22 PM, Rémy Oudompheng <remyoudompheng@gmail.com> wrote:
On 2011/6/19 Dan McGee <dpmcgee@gmail.com> wrote:
I think some drivers don't (didn't?) support switching modes if the interface is up, or something like that?
So more precisely, the question is probably: is wpa_supplicant capable of manipulating interfaces that are down, just like iwconfig?
I have an iwl3945, so I could help with testing. However, I'd need someone to tell me what setups to test and what problems to look for.
-t
I'm stupid since I have a iwl3945 myself. The test setup is the following: - set up your card in a stupid mode (iwconfig wlan0 mode Monitor) - try to start a netcfg profile without it using iwconfig. I'll upload my latest changes to the no-iwconfig branch for you to test. I've successfully managed to do it by moving the interface_up part *after* starting+configuring wpa_supplicant, so it seems to indicate that wpa_supplicant is able to switch modes itself. However i'm not sure it works for any setup. -- Rémy.
Am 19.06.2011 18:13, schrieb Rémy Oudompheng:
Hello,
wpa_supplicant is supposed to provide most of the wireless_tools functionality. I have set up a branch of netcfg that replaces all uses of wireless_tools by wpa_supplicant.
http://projects.archlinux.org/users/remy/netcfg.git/log/?h=no-iwconfig
iwconfig is still used by the deprecated IWCONFIG option, but there is still one thing I don't really understand.
You can use iw to configure wireless options. You can also use iw instead of iwconfig for the wep-old and open-old modes.
In src/connections/wireless, there is block that calls "iwconfig mode Managed" before starting wpa_supplicant. The log is not really explicit about why this was added (it merely says it was necessary for iwl3945), and wpa_supplicant man page only says it's necessary for the hostap driver, which we do not use. Does anybody knows the reason why it is needed?
This isn't needed, this looks like a workaround for very early linux wireless drivers.
On 2011/6/19 Thomas Bächler <thomas@archlinux.org> wrote:
You can use iw to configure wireless options. You can also use iw instead of iwconfig for the wep-old and open-old modes.
Thank you, I'll look into it if any of its features are needed. For the moment wpa_supplicant seems to do the job. Rémy.
participants (5)
-
Dan McGee
-
Rémy Oudompheng
-
Rémy Oudompheng
-
Thomas Bächler
-
Tom Gundersen