Date: Thu, 04 May 2006 15:50:36 +0100 From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> To: "Marc G. Fournier" <scrappy@hub.org> Cc: Rutger Bevaart <rutger.bevaart@illian-networks.nl>, freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... Message-ID: <1146754236.4321.26.camel@buffy.york.ac.uk> In-Reply-To: <20060504112918.Q1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> <A7201732-7F1A-45B1-98DF-003303A0DBAF@illian-networks.nl> <20060504112918.Q1147@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: > 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 :( ... or use ports/net/arping: arping -S <new IP> -s <your-MAC> router-IP But, I agree, this is a bug with em(4) that should probably be fixed at some point... Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1146754236.4321.26.camel>