sathya sai put forth on 12/22/2009 3:17 AM: > Hi Stan, > > I have already thought about this. But the problem here is, we dont have > a control over neither over our DHCP server nor the system which > statically configures the IP address in our subnet. I hope that, this > true even with the real time deployment scenario.
That's what I figured. > So, to overcome I will that it would be better if our dhcp client does > an ARP broadcast to detect an IP conflict (as per RFC 2131) and send > DHCPDECLINE if it has found IP conflict. > > Could you please let me know your thoughts on this. Sure. First, talk to the people in charge of your network, and ask them to create a dhcp reservation for the host with the static IP. The problem you have is not technical in nature, but administrative. Second, have you confirmed that your Debian client is in fact not sending the decline packet? Or are you just assuming this? How do you know it's not sending the decline packet but the dhcp server isn't responding and offering a new address? If the server doesn't respond to the decline, I believe the default dhclient behavior is to use the first address given by the dhcp server. Unless you grab some packets you won't really know what's happening. Have you applied tcpdump to this problem, or another packet sniffer? Also, you haven't posted any relevant log information. It's difficult to diagnose a problem without seeing the error messages in the log file(s). -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
