[PATCH] udhcp: infinite retries

[Samuel Ortiz]

Paul Fox wrote:
>  > >>> It may be useful (at least it is for us) to keep on sending DHCP request 
>  > >>> and renewals for ever until we actually get an answer. For that purpose 
>  > >>> udhcpc -t 0 could do the job.
>  > >> I guess udhcpc -t 999999999 will be the same in practice.
>  > > 
>  > > Almost, but not exactly.
>  > > We have machines that can be powered up without being connected to any 
>  > > network for weeks. However, we need them to fetch an IP if they ever get 
>  > > plugged to some network.
>  > 
>  > Then maybe you want to use something like netplugd ot ifplugd ...
> 
> of course that takes care of the locally connected problem, but
> not the "connected to a switch which is itself disconnected"
> problem.  but i agree -- if it were me, i'd probably use a
> combination of the mechanisms.
well, with the infinite retries option, we can live without netplugd.
However, I agree that it would be nicer to have netplugd firing up 
udhcpc with infinite retries whenever we actually are plugged/associated 
(we do have machines with both ethernet and 802.11 interfaces).

Cheers,
Samuel.


> dhcp should be using netlink itself, to track interface connectivity.  (i.e.,
> needing ifplugd is a bug, in my opinion.)
> 
> paul
> =---------------------
>  paul fox, pgf at brightstareng.com
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>