Excerpts from Gerhard Brauer's message of 2010-11-09 14:55:53 +0100:

Hi,

our current default wireless framework in base /e/rc.d/network script is iwconfig (Open/WEP only). I like to integrate wpa_supplicant as easy as we could use iwconfig ATM.

iwconfig is a useless framework in most user environments in these days (most AP's have a stronger encryption than WEP'), but it is a "easy" tool.

Two possibilities: a) Throw away iwconfig(wireless-tools package) from rc.d/network and use wap_supplicant only. wpa_supplicant could of course do all the things iwconfig is for.

b) Let the user decide wihich wireless framework. This could be done by seperate /e/conf.d/wireless from wireless_tools and add therin config options for each iwconfig and wpa_supplicant. Ex.: -------------------- #wlan_eth0="iw|eth0 mode managed essid default" #wlan_wlan0="wpas|"

#WLAN_INTERFACES=(eth0 wlan0) ------------------------- So /e/rc.d/network->wi_up() has to be modified to honor also wpa_supplicant.

For both ways /e/wpa_supplicant.conf should get modified to a cleaner default config (Most comments and examples). We should provide a config file with activated entries for OPEN wlan and WEP connections (User has to modify WEP essid and key), and also a deactivated entry for common WPA2/PSK wlan(User has to modify and activate this for his/her needs).

The advantage of using wpa_supplicant at least in addition to iwconfig is IMHO the easy and straightforward integration in our network settings (r.conf and conf.d/wireless). No need for extra packages like Netcfg, wicd, networkmanager to associate to WPA infrastructure (but could be used by users if they want their "funcionality"").

What do you think about?

Regards Gerhard "gerbra"

I had trouble with wicd and looked for other solutions, and I really wondered about the open/WEP thing, because it's imho rather useless. Would any sane person still use WEP if they have WPA2 available, which is most likely the case these days? I now use wpa_supplicant directly and it works fine, but there seem to be some troubles with dhcpcd (not running after boot, needs to be re-enabled after switching network/interface, most of the time). Well, maybe a little scripting can take care of that.

I have a wireless printer, which only takes WEP... Also, not all gateways support WPA2 reliably (e.g. Verizon ActionTec devices). On (11/09/10 17:19), Philipp Überbacher wrote: -~> Would any sane person still use WEP if they have WPA2 available, which -~> is most likely the case these days? -- lisaev@svibor

On Tue, Nov 09, 2010 at 10:42:16PM +0100, Thomas Bächler wrote:

Am 09.11.2010 14:55, schrieb Gerhard Brauer:

...

Hi,

Hi Gerhard, it is nice to hear from you after such a long time :) Yeah, no more R.I.P (rest in pieces), or: "Auferstanden aus Ruinen..." ;-)

...

our current default wireless framework in base /e/rc.d/network script is iwconfig (Open/WEP only). I like to integrate wpa_supplicant as easy as we could use iwconfig ATM.

All existing features should be ported to netcfg, and new features will only be added there. Again, lack of time prevents me from doing that too - but it's the plan.

Ok, i'm fine with. Have used netcfg last before ~2 years or so, it is currently much better. I will have a deeper look next weeks (on the bridging part, maybe i could add VPN support on that easy way...)

Back to the topic of wireless: netcfg's net-auto-wireless mode is my favorite and works perfectly for me.

Yes, also together with net-auto-wired it works fine. I'm only not sure if i use network-profile seperate configs or better go with wireless-wpa-config ("static" /e/wpa_supplicant.conf) cause i often use wpa_gui with option to update the config. Also i will use different "actions" based on different DHCP server's and/or MAC addresses found by the active devices. But this seams also possible (without more work than one need for ifplugd as single tool...) Regards Gerhard