In message <20031220153144.6234C16FAC@mail.nitros9.org>, "Alan DeKok" writes:
>"Steven M. Bellovin" <smb@research.att.com> wrote:
>> Hmm....  It's not an authentication issue -- I don't run EAP in my 
>> house -- but I see your point.  But you raise an interesting 
>> architectural point: how to manage non-static connectivity.
>
>  On Linux systems, there are scripts which run when an interface goes
>up or down.  e.g. ifup-eth0: start a dhcp client.  ifdown-eth0: kill
>the dhcp client.

We could very much use *something* that received events for such things.
>
>>. ..  I'd love to be able to do something similar on NetBSD,
>>including caching authentication credentials if possible and
>>necessary.
>
>  I don't think it's hard to do, it's just that I don't know if it's
>been done yet in NetBSD.
>

I've tried playing a bit with the OMAPI interface to dhclient, but I've 
never gotten it to work.

		--Steve Bellovin, http://www.research.att.com/~smb