Date: Thu, 4 May 2006 10:20:59 +0200 From: Rutger Bevaart <rutger.bevaart@illian-networks.nl> To: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... Message-ID: <A7201732-7F1A-45B1-98DF-003303A0DBAF@illian-networks.nl> In-Reply-To: <20060504070534.98F0216A432@hub.freebsd.org> References: <20060504070534.98F0216A432@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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). Sounds like a bug in the em driver. Anybody do sniffing to see if it does send out ARPs? If not I can test on one of our Dell 2850's with em's. Regards, Rutger Bevaart > Date: Wed, 3 May 2006 21:43:39 -0300 (ADT) > From: "Marc G. Fournier" <scrappy@hub.org> > Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... > To: freebsd-stable@freebsd.org > Message-ID: <20060503214233.G1147@ganymede.hub.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > Also, as an aside ... 6.x em(4) still isn't sending up the arp > broadcasts, > so IPs moved from one machine to this one aren't having their routes > appropriately updated ... again, please note, that moving an IP > from any > machine to a *non* em(4) interface does update the routes properly and > instantly ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A7201732-7F1A-45B1-98DF-003303A0DBAF>