arp messages: Why is this happening?

[Mark Atkinson]

This is probably a DHCP network?  This would happen if a client gets a 
new DHCP assigned IP address, instead of it's old one, and before the
freebsd boxes' ARP cache expired for that machine.  Usually this only 
happens with:

- broken DHCP clients (not requesting it's old ip back upon reboot).
- broken DHCP servers (not maintaining lease state properly to
                        assign clients their old addresses)
- tight DHCP address spaces (ie. the DHCP server must reuse previously
                              leased IP addresses to accomodate
                              new DISCOVERS).

or a combination of the above.

Either that or you have a whole bunch of machines that use gratuitous
ARP to advertise the new interfaces in a failover situation.


ODHIAMBO Washington wrote:
> My log files (and console) fill up with these messages.
> 
> 
> 
>>arp: 62.8.64.172 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1
>>arp: 62.8.64.201 moved from 00:c0:05:10:01:f1 to 00:c0:05:11:01:f1 on bge1
>>arp: 62.8.64.201 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1
>>arp: 62.8.64.145 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1
>>arp: 62.8.64.212 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1
>>arp: 62.8.64.188 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1
> 
> ...
> 
> 
> Googling doesn't seem to give me a good answer as to why.
> This is 4.8-STABLE
> 
> 
> 
> 
> -Wash
> 

---
Mark
atkin901 at NOSPAM yahoo dot com
(!wired)?(coffee++):(wired);