[pkg-wpa-devel] action script timout (was Re: wpasupplicant experimental branch)

[Kel Modderman]

Reinhard Tartler wrote:
> On Mon, Mar 27, 2006 at 08:08:55PM +1000, Kel Modderman wrote:
>   
>>> How do you make sure that the interface gets an ip via dhcp before running
>>> any other scripts besides wpasupplicant? This is a quite important
>>> point, because at least in ubuntu, interfaces are always ifupped via
>>> udev, so there is no difference between hotplugged and not hotplugged
>>> interfaces. Many other daemons like openvpn and ntpdate are running from
>>> scripts in /etc/network/if-up.d. We need to make sure that
>>> /etc/network/if-pre-up.d/wpasupplicants blocks until the interface got
>>> an ip or was configured by alternate means. (e.g. statically).
>>>       
>> This complexity must be managed by the user, if the user expects to 
>> connect to various different wireless locations and run those sort of 
>> things, it is expected that (s)he knows what (s)he is doing, IMHO.
>>     
>
> No, I disagree at this point. Even (and espc.) for simple cases, we MUST
> ensure that after if-pre-up.d, the interface has an ip is ready to
> transit data. The action script is handy when the user changes his
> location, okay, but we really should at least try to wait for getting a
> dhcp lease before handing control back to ifupdown. Thats why I put
> 'dhcp' instead of 'manual' in my interfaces line, so that ifupdown calls
> dhclient to get an ip before calling the rest of ifup.d. So I suggest to
> suggest using 'dhcp' instead of 'manual' for easy cases, because I don't
> see how the action script can solve that problem.
>   

Problem solved :-)

Kel.