linux does not response gratuitous arp request?



I'm testing dhcp with conflict ip.
As my understanding, when dhcp server assign an IP to a windows
PC(pc1), pc1 will send out an gratuitous arp to confirm if there is
another PC using the IP. if another PC(linux,pc2) is using the IP,
then pc2 should send out an arp reply to claim it's using it, then pc1
will send out dhcp decline packet to dhcp server and request another
IP.

But, in my test, pc2 does not response the gratuitous arp request at
all, why? if PC2 is windows OS, it will response it. So, for the
linux case, IP address conflict problem will occur. Is this by
design? (if it is, how can we avoid the address conflict problem?)

another problem is : when a linux PC was assigned a new ip, it will
just use it anyway, without sending gratuitous arp to check if there
is a conflict, but windows PC will.

Why does the linux and windows behave different so much?

Thanks

.



Relevant Pages

  • Re: linux does not response gratuitous arp request?
    ... when dhcp server assign an IP to a windows ... PC(pc1), pc1 will send out an gratuitous arp to confirm if there is ...
    (comp.os.linux.misc)
  • Re: linux does not response gratuitous arp request?
    ... when dhcp server assign an IP to a windows ... pc1 will send out an gratuitous arp to confirm if there is ... But, in my test, pc2 does not response the gratuitous arp request at ...
    (comp.os.linux.misc)
  • Re: Can ping out, but cant be pinged
    ... The computer can be seen in Windows Explorer ... LSP / Winsock corruption is another good possibility. ... The problem came up when I used Norton Ghost to move the contents of a hard ... choices are outside the scope of the DHCP server? ...
    (microsoft.public.windowsxp.network_web)
  • RE: Offline Files
    ... After you resolve an offline files synchronization conflict by using the ... the conflict occurs again on a Windows ... click to check the "Hide All Microsoft Services" ...
    (microsoft.public.windows.server.sbs)
  • Re: IRQ BSOD
    ... You receive a "Stop 0x0000000A" error message in Windows XP ... could be a faulty memory problem or a driver conflict problem. ...
    (microsoft.public.windowsxp.help_and_support)