dhcpcd-discuss

Re: IPV4LL and EXPIRE

Roy Marples

Fri Oct 24 20:02:34 2014

On Thursday 23 Oct 2014 21:28:33 Roy Marples wrote:
> On Wednesday 22 Oct 2014 16:07:49 Roy Marples wrote:
> > On 22/10/2014 16:01, David Hauck wrote:
> > > I wonder if this behaviour should be configurable?
> > 
> > No.
> > 
> > I actually had a better idea and am working on making a better ARP state
> > engine, so we can have two, one for DHCP and one for IPv4LL.
> > This should allow dhcpcd to negotiate DHCP and IPv4LL at the same time.
> 
> This has now been done.
> 
> DHCP will start.
> After 5 seconds IPv4LL will start.
> 
> So far, I've only tested that it works - I still need to test conflict and
> defence for IPv4LL.

I've fixed a few bugs since the initial patch and it now seems very stable and 
reliable. Valgrind is reporting no memory errors as well.

The intial reported issue remains solved while allowing concurrent DHCP and 
ARP requests :)

Testing of the trunk tarball would be nice at this point, just incase I've 
missed something silly :)
http://roy.marples.name/projects/dhcpcd/tarball/dhcpcd-trunk.tar.gz

Thanks

Roy

Follow-Ups:
RE: IPV4LL and EXPIREDavid Hauck
References:
IPV4LL and EXPIREDavid Hauck
Re: IPV4LL and EXPIRERoy Marples
Re: IPV4LL and EXPIRERoy Marples
Archive administrator: postmaster@marples.name