On Thu, 4 May 2006, Rutger Bevaart wrote:
Technically it's not routes that are not being updated, but a stale (outdated) ARP cache on the other hosts. The system with the new alias'ed IP needs to do a gratuitous ARP (broadcast ARP for it's own IP). As an intermediate solution you could flush the ARP cache on the hosts with stale cache (usually a router or L3 switch on the subnet).
This is what we end up having to do ... but, unfortunately, that means getting ahold of our co-lo provider and asking them to do it ... they have always been most accomodating, its just one of those things that I shouldn't *have* to do :(
---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
