[pkg-wpa-devel] Re: wpasupplicant experimental branch

[Kel Modderman]

Reinhard Tartler 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.


> I took a closer look to the dhcp action script. I noticed that when
> roaming, the dhclient does not reliably request a new lease when getting
> disconnected. I'm not sure why this happens, but I really think we
> should signal a running dhclient daemon that we want the lease to be
> renewed when we connect to a new location.
>   

It releases the device on disconnect events very reliably here, and 
renews a lease or asks for a new lease at each connect event, also 
reliably here. I'm not sure i see your problem yet, maybe time will tell 
(and more intensive testing). But this script is just "proof-of-concept" 
really, and will not be the default mode,  but simply a nice enhancement.


>> b) i think that the dhclient script is quite useful to a large 
>> percentage of users, why not keep a dpkg handle on that file instead of 
>> forcing the user to manually copy an example script to a more suitable 
>> location?
>>     
>
> So you do want to make it active by default?
>   


Putting words into my mouth; no.


> I don't want the default action script to be a conffile for this reason:
> I expect many users to customize/edit that script to include local
> configuration. If this happens, they will be bugged on every upgrade.
> Therefore I suggest that if we don't intend to make it active by
> default, to not ship it in /etc, so that we don't need to care about
> conffile handling at all.
>
> If we do want to make it active by default, I'd like to provide some
> means of overriding it with a local version but without needing to touch
> any conffiles, so that upgrades go smoothly.
>   

Now that is a great argument, and I completely agree, we should *not* 
mark them as conffiles, thus, they do not belong in /etc.

I never intended an action script to be default mode, this should all 
remain optional.


>>> just a glitch: could we please provide some symlinks from
>>> /usr/sbin/wpa_supplicant to /sbin/wpa_supplicant for transitional
>>> purposes? This broke my former home made scripts.
>>>  
>>>       
>> Strong ack. Will do that immediately.
>>     
>
> Already done ;)
>
>
>   

Thanks


>
> No problem, I'll respect that and ask you before every upload :)
>   

Thanks, Kel.