dhcpcd-discuss

RE: IPV4LL and EXPIRE

Roy Marples

Mon Oct 20 19:26:45 2014

On 2014-10-18 01:16, Roy Marples wrote:
So that's the reason maybe? Defending the IPv4LL address triggered an expiry?
I may have to setup a reverse ARP proxy to test this.

Fixed here:
http://roy.marples.name/projects/dhcpcd/ci/77cc5e6fefbda2e0d03790a2cd1447df385c2d18?sbs=0

Hopefully that fixes the state engine, can you test it please? :)

So the last question is how do we handle the ARP table?
From your earlier statements, it looks like you run dhcpcd per interface rather than once dhcpcd process for all interfaces. Is this true? Also, what kernel are you running? I thought that deleting the IP address would clear the ARP entry for it? If this is the case, how did the table fill up unless IPv4LL from other machines?

Hopefully you can clarify all the above!

Thanks

Roy

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