On Mon, Dec 29, 2008 at 06:10:18PM +0000, Csaba Henk <[email protected]> wrote: > Because it makes you specify a parameter manually which could be easily > found out by the computer. If you usually use two wireless networks, one > with essid, say, Formalhaut, and other with essid Locris, then that dumb > box can decide which one to use by iterating over the list of available > networks and see if the list contains an access point named Formalhaut > or Locris and you don't need to interfere. Moreover, this utter > cleverness is actually implemented by wpa_supplicant. This > one-essid+wpa_psk-per-profile scheme is just a step back; it's a > renouncement of relying on the niceties of wpa_supplicant. > > (OK, I don't know if wpa_supplicant can handle the case when the > wireless network is named Linksys at both scenes, etc etc. I don't say > you never need multiple profiles, but I do think in most cases it's > not necessary to have to choose manually between profiles.) > > So, I'd say, at the end of the day, many users want a setup which works > like the one with the hooks for wpa_supplicant (though maybe they don't > know of or think into or care about it). There should be a more > streamlined way to get at this.
I didn't know about this feature. Am I right about then - in case you just use WPA in both profile and you use the hook method, then you can avoid both the passwords and the essid in the netconfig profile? In that case I think a possible solution would be - on top of the "notice about automatic generation" patch: 1) in libfwnetconfig, handle the - for example - 'wpa_psk = config' value as a special one: that would tell the lib to start wpa_suppliciant but not set the essid nor touch the config 2) in netconfig: if the interface is detected as a wireless one, then before asking for essid, ask if the user wants to use an existing wpa_suppliciant.conf. a) if yes, then just set wpa_psk to config, and we're done. (no question for esddi/wep/wpa driver / wpa psk) b) if no - this would be a sane default, since unencrypted and wep networks are still commonly used - then just go along with the old behaviour. Both suggestions are in a "if you care to send a patch, that's the best, but with some time delay I can do it as well if you don't want to do it".
pgp4nX8vmeIj9.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
