[openbeosnetteam] Re: DHCP Project Specs Needed

Philippe Houdoin <philippe.houdoin@xxxxxxx> wrote:
> Quoting David Enderson <DEnderson@xxxxxxxxxxxxxx>:
> > I mentioned a while back on this list that eventually a way will be 
> > needed to
> > provide for expired DHCP leases, which means something like a 
> > background
> > process or cron script.  The solaris implementation solves the 
> > lease issue by
> > having the DHCP client be a daemon.
> All options are opened to us too in fact:
> - a userland background process (daemon)
> - a kernel daemon, registered by the network stack module handling 
> DHCP, awake
> by kernel daemon thread after lease expiration time
> - a timer callback registered by the network stack module handling 
> DHCP, using
> our network stack's timers support, already used by our ARP protocol 
> code to
> handling IP <-> MAC addresses request & cache expiration timeouts
> 
> I rather like the latest solution, reusing network timers feature.

Is there any situation where the DHCP negotation has to be started by a 
kernel component? If not, I would rather put it in userland.
Don't we need a replacement for inetd anyway? Couldn't we have a 
net_server that takes over inetd services as well as DHCP (as an add-
on, possibly)?

Bye,
   Axel.

Other related posts: