Date: Wed, 21 Jan 2004 08:59:49 -0600 From: "Jack L. Stone" <jackstone@sage-one.net> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Mark <mark@s-wit.net> Cc: freebsd-security@freebsd.org Subject: Re: arp problem in /var/log/messages Message-ID: <3.0.5.32.20040121085949.01e93e00@10.0.0.10> In-Reply-To: <Pine.BSF.4.53.0401210552530.94399@e0-0.zab2.int.zabbadoz.n et> References: <00dd01c3dfd6$2a7e1fd0$65a8a8c0@toshibauser> <09bd01c3ddbc$9f829070$fa10fea9@bryanuptrvb0jc> <20040118.184351.3b20743ee03ef7d3.10.0.3.9@bugsgrief.net> <00dd01c3dfd6$2a7e1fd0$65a8a8c0@toshibauser>
next in thread | previous in thread | raw e-mail | index | archive | help
At 05:53 AM 1.21.2004 +0000, Bjoern A. Zeeb wrote: >On Tue, 20 Jan 2004, Mark wrote: > >> But what causes them ? I get them too. > >one host, two NICs same braodcast domain ? > >-- >Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Also, when NICs are switched around, especially if on a gateway machine. We just experienced this maddening issue. We moved a HD clone from one GW machine to another and it took a long time for any of the other machines to resolve the new NIC MAC and thus peppered with those arp messages. When we also moved the old NIC over as well, the problems ALL stopped instantly. It eliminated the need for the arp cache to catch up to the switching of the MACs which is cached along with the IPs. All of the machines then settled down. So, now with a CISCO and several switches involved, we now know the move the HD AND the NIC.... BTW, the Windows machines never did resolve the new NIC MAC after several hours, but the FBSD's did within about an hour. Lesson learned. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20040121085949.01e93e00>