Joerg Platte wrote:
Package: wpasupplicant
Version: 0.4.8-1
Severity: wishlist

Hi!

I'm using wpa_supplicant and ifplugd. Each time, wpa_supplicant is able to
associate with one of my preconfigured networks, ifplugd detects this and 
invokes
"ifup interface". In /etc/network/interfaces I'm using some mappings to
select the current network based on the ESSID (different configurations with
different debian mirrors and proxy settings exist):

mapping ath0 wlan0
        script /usr/local/sbin/guessnet-wlan
        map HRZ\ WAVE-LAN wlan-hrz
        map jako wlan-jako
        map POLLE.home wlan-polle

With the newly created configuration modes I can't use this configuration
any more (please give me a hint if I'm wrong :-). Can you provide the "old"
startup links and configuration file as a third option? Otherwise I must
simply reactivate the old scripts, but this may result in some problems in
the future which may occur on package changes.

Hi Joerg,

I have some thoughts to implement some sort of network profiling using only callbacks from wpa_cli. I'll try to get together some sort of code for you to try soon. After the last release I've taken a little breather to collect my thoughts, it was a hectic two weeks.

Personaly, I had no objection to the init script being included, but not active. However, it had severe limitations, and as new programs emerge, that can handle your wifi profiles (eg. network-manager) using far superior methods than an init daemon + ifplugd (or whatever), it is important that we move on with some lower level integration of wpa_supplicant with out networking scripts, imho.

Having said that, its possible to provide a simplistic method of wifi profiling, by calling for information from wpa_cli and executing different network specific operations. The framework is already there, using the manual inet METHOD plus an action script. The hard part is fooling ifupdown into going along with such plans . . .

Thanks, Kel.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to