[pkg-wpa-devel] Question regarding the new config scheme

[Kel Modderman]

Reinhard Tartler wrote:
> I wanted to post this answer to another thread, but this place fits as
> well:
>
> I think the init script itself does not get you anything. People that
> are complaining that it has gone are rather complaining that their
> setups which involve ifplugd (with or without guessnet) won't work with
> wpasupplicant controlled by ifupdown, and I havn't read any other
> argument so far.
>   

Me neither.
> FWIW, people who complained on this want to implement a roaming
> solution, which wpasupplicant is in fact capable of in some cases. The
> initscript alone however, is only a part of that solution. The other
> part is left on the user side: integration of ifplugdown and guessnet.
>   

Which never was officially documented, hence why I bothered to hack up 
this ifupdown solution.

> I really think that the package wpasupplicant should be left simple as
> it is now. Unlike as in sarge, there are now reverse dependencies like
> network-manager, which just need the wpasupplicant binary and care for
> the rest. The init script was part of a solution, which doesn't belong
> to the 'core' package itself anyhow (imo).
>
> Let's do it properly, and create a new binary package which uses
> wpasupplicant as controlling daemon. It should communicate with the user
> via debconf, and ask him if and which interface he wants do have
> managed. It should also enable ifplugd [1] semi-automatically. It would
> be really great if it could also enable the user to create /e/n/i
> stanzas suitable for guessnet integration, I'd prefer it to be
> debconf-driven. This should really warrant a binary package of it's own,
> if not perhaps a small new debian native package.
>   

Sure, this would be the best and most proper solution by far.

Thanks, Kel.