0

In my opinion, as the 2131 says, DHCP server will send ICMP to the ip before send it to client, and if that icmp is replied, server will send another ip. Thus I think,once there's a conflict(like someone manually set the same ip on another host in vlan while that ip was already gotten by dhcp client), server should be able to detect that conflict as soon as it first time received the REQUESE from client, and distribute a new ip to client. But in my case, server still ack that conflicting ip to dhcp client.

I had a hub connected with a dhcp server(debian 8) and hosts A . Then I had dhcp-server given hostA 192.168.2.170 automatically. Next I set the interface of a hostB with the same ip 192.168.2.170 manually, and up that interface to that hub, but not only hostB can ping the server(maybe 40% loss), but also A would still be able to renew that 192.168.2.170 from server successfully (I used wireshark and found that server already known that ip is duplicated, not by ICMP, but arp)

My question is, if my case happens, how does isc-dhcp-server do detection? Does isc-dhcp-server be able to handle this case, which one in vlan is set the same ip after which have already been given to a client?

  • I'm asked to come up an idea in case that situation cause problems... – YH Wang Dec 14 '17 at 2:48
  • 1
    I'm not totally sure but I think it stores the automatic provided IPs together with the devices MAC address so as soon as a MAC is registered with a certain IP it will not check again if meanwhile this IP was taken by another device without DHCP. – derHugo Dec 14 '17 at 6:23
  • You can anyway "reserve" this IP in order to make sure the same IP is not available for DHCP anymore: askubuntu.com/a/392635/423684 – derHugo Dec 14 '17 at 6:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.