On Thu, Apr 06, 2006 at 06:02:05PM +0200, Steen Krøyer wrote:
> My system: Debian unstable, customised kernel 2.6.15, ipw2200 1.1.12.
>
> The latest changes in wpasupplicant (0.4.8-1 and 0.4.8-2) broke
> wpasupplicant for me. The problem seems to be that ifup fails to
> set all the params (environment variables) needed by
> /etc/wpa_supplicant/ifupdown.sh.
So you are really sure that you are comparing 0.4.8-1 to 0.4.8-2? I'm a
bit confused, because you say this:
> So the script bails out because there's no $IF_WPA.... set.
> If ifup is not supposed to set all the necessary params,
> presumably some other script is needed
ifup IS supposed to set these $IF_WPA_* options, iff the user sets the
wpa commands in /etc/network/interfaces as documented in
/usr/share/doc/wpasupplicant/README.Modes.
> Is wpa-conf something one is assume to install when using
> wpasupplicant? The Debian site or Google reveals nothing
> about wpa-conf. I can of course whip up my own script (I
> have in fact done so to get my wireless lan up again).
if you want to use wpasupplicant from ifupdown, then you are supposed to
provide wpa-* statements, according to your local network configuration.
If you don't provide any wpa-* configuration in /etc/network/interfaces,
wpasupplicant won't be started by ifupdown (and you're free to have
wpasupplicant started by your own written scripts, as you like).
I'm quite confused because this behavior was also in 0.4.8-1. Did you
perhaps miss to read /usr/share/doc/wpasupplicant/NEWS.Debian?
Gruesse,
Reinhard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
