Re: dhcpcd 7.0.8 - Device did not check if it's original address was in use before probing for a new address
Roy Marples
Fri Jan 18 20:54:33 2019
On 17/01/2019 23:38, Stefano Cappa wrote:
I applied both patches and its working. very good.
PS about subsequent conflicts I created a report with wireshark. I hope
its enough, otherwise I'll create a report from the beginning of the
test and not only subsequent conflicts.
Trace looks fine. We see this:
dhcpcd (assuming FreeScale MAC) announces 169.254.19.151
test tool (assuming ReaTek MAC) conflicts 169.254.19.151
dhcpcd defends 169.254.19.151
test tool (assuming ReaTek MAC) conflicts 169.254.19.151
dhcpcd gives up and probes new address 169.254.122.252
So this warning:
> *WARNING 19:58:52.757124: NOTE: Device did not wait for second conflict
> probe before selecting a new address.*
Is a lie.
Now it might be a bug in the testing tool, or something else send a
duplicate ARP other the interface. We don't know, all we do know is that
from the dhcpcd log AND the wireshark trace, dhcpcd is performing as per
the RFC.
> As you can see this is not a real error, but Apple asks what you are
> doing to fix this in the future. So they tolerate this warning, but only
> if you are working to try to fix it in next firmware releases.
Same question, back at Apple :)
If you're happy with this, I'll release a new dhcpcd over the weekend as
one is long overdue at this point!
Roy
Archive administrator: postmaster@marples.name