dhcpcd-discuss

Re: timeout behavior different with dhcpcd 6.6.1

Roy Marples

Thu Nov 13 15:50:40 2014

On 13/11/2014 15:25, Amit Uttamchandani wrote:
> On Thu, Nov 13, 2014 at 11:58:59AM +0000, Roy Marples wrote:
>> This looks like a bug and I'll try and look into it when I get the chance.
>> For the time being, you can disable IPv4LL by adding noipv4ll to the top
>> of dhcpcd.conf to hopefully get the behaviour you desire.
>>
> Thanks Roy. Unfortunately, we use the IPv4LL functionality. But it's ok,
> I will wait for your fix.

OK, fair enough.
Tell me though, when the IPv4LL address was assigned with timeout 0, did
it get a lease assigned to the interface shortly afterwards?

> The reason we needed to upgrade was because in 6.0.5, dhcpcd would not
> send DECLINE messages back to the dhcp server when it was offering it
> address that was in conflict. Thus, it would get into a loop where
> dhcpcd would keep asking for an offer and server would give it same
> address over and over again. In 6.6.1, dhcpcd sends decline messages,
> thus, server ends up offering it new address.

Progress for your use case at least :)

Roy

Follow-Ups:
Re: timeout behavior different with dhcpcd 6.6.1Amit Uttamchandani
References:
timeout behavior different with dhcpcd 6.6.1Amit Uttamchandani
Re: timeout behavior different with dhcpcd 6.6.1Roy Marples
Re: timeout behavior different with dhcpcd 6.6.1Amit Uttamchandani
Archive administrator: postmaster@marples.name