dhcpcd-discuss

Hi

On 03/05/2016 13:27, Shahid Mahmood wrote:
> I am trying to test duplicate IP address detection. Started dhcpcd as
> usual, found out what IP address it got, then manually assigned that
> address to another host on the network. After that, I did arping and
> normal ping from the duplicated-ip-host, but there is no indication or
> event received on the machine running dhcpcd. The reason stays at
> "BOUND" and 'new_ip_address=' remains to keep showing the same
> (duplicated) IP.
> 
> Does anyone know how this feature is actually tested? What should be my
> expectations from dhcpcd?

dhcpcd DaD behaviour mirrors that of kernel IPv6 DaD in-that DaD is only
performed when the address is initially assigned to the interface.
As you say, you assigned the same IP to another node after dhcpcd
assigned it's address, so here dhcpcd will do nothing.

> (testing on the latest trunk)

The latest trunk still behaves the same way, but for IPv4 it keeps the
ARP socket open and will warn via syslog about DaD conflicts but it
won't do anything else about it because I've not decided what that
action should be as yet.

In the DHCP server not responding and lease expired case dhcpcd will now
drop the lease on DaD failure.

Roy