[pkg-wpa-devel] A challenge: wpa_supplicant + wlan button + zeroconf

[Felix Homann]

On Wednesday 12 April 2006 09:05, Reinhard Tartler wrote:
> Could you please explain why zeroconf breaks the scenario you described?
> the issues seem unrelated to me.

Hmm, that's a misperception. Zeroconf doesn't break anything. It's just that 
the new approach of wpasupplicant doesn't seem to be suitable for the simple 
needs I've described.

Here again is the information on the issues I have (new comments in * * ):

1.  With this setup zeroconf will run on the interface. I won't get an IP via 
DHCP *no matter if there is a DHCP server or not*. I have to increase 
wpa-action-timeout to prevent this.
2. If I increase wpa-action-timeout boot will hang for the given time if the 
radio is switched off or there is no configured AP. *waiting for the action 
script to finish*
3. If I don't set wlan to auto I have to manually ifup the interface, i.e. I 
have to login.

I guess that lowering the timeout to -1 (and even a few positive seconds) 
makes zeroconf think that DHCP has failed. It therefore provides a LL 
address.

If that's the case it just shows that setting the timeout to -1 is a dirty 
workaround to avoid issue #2 which it indeed is.

In the "mode 3 daemon"+ifplugd setting the interface is only brought up if 
there actually _is_ an AP, waiting for the DHCP server to answer is OK then. 
Boot won't hang if the radio is off or there's no AP. Only if the DHCP query 
really times out zeroconf will jump in.

Regards,

Felix