The forums periodically raise the issue of the operation of networks containing the same IP addresses in one physical segment. It turns out the so-called conflict of IP addresses on the network. After reading many of these forums, it becomes clear that not everyone understands this process correctly, so many people begin to pass off various facts and conjectures as facts that are far from the truth. Not so long ago, on one excellent resource of system administrators, this issue was heatedly discussed. In this regard, there was a need to somehow clarify the urgent situation. The format of the forums is the exchange of chains consisting of questions and answers to them, and in the article you can talk about everything in sequence.
Conflicting IP network addresses and network protocols
, , ARP. . IP ARP. , IP DNS . , SPA TRA . , IP . , , , . , , ?
, , , , , . ?
. IP , , , . , . DHCP, , DHCP- DHCPOFFER. , , DHCPOFFER , DHCPDECLINE DHCP-. , . ip , DHCPDISCOVER.
IP . , SPA, . , . ip , . . : . .
It is important to understand that the exchange of data requests and responses is made only when the address is initialized. If, for example, the node was configured to a conflicting address before it connected to the network, then after it is turned on, there will be no exchange of data with voluntary requests. In this regard, this conflicting address will be used by both nodes of the network, but with each new ARP request, both nodes will generate an error about conflicting addresses.