This behavior is consistent with most IOS based routers I've worked around, they typically hold onto an ARP entry for about 20 minutes before expiring it. On linux I've used a network utility called send_arp that can shoot a user specified gratuitous arp packet at another host on the same layer2 network. I'm sure there are other tools available to do the same from freebsd (if you don't have administrative access to the cisco to clear the arp cache). I'm not sure if I like cisco routers by default being willing to accept an arp response that it didn't request, but that's a different issue.
On Fri, 25 Jun 2004, Peter Pauly wrote: > This morning while attempting to replace a server with a new machine > (same IP address, the old machine was unplugged), The Cisco 2600 > router's arp table continued to point to the old DNS server's MAC > address. > > Even after rebooting the new server (Freebsd 5.2.1), the MAC address > remained unchanged in the router. The router continued to point to the > old machine's MAC address. > > I updated the entry manually in the router and all was well. But I am > concerned that Freebsd is not announcing it's MAC address when the > machine or interface comes up. Any ideas? > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"