From owner-freebsd-stable@FreeBSD.ORG Thu May 4 14:30:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ACC216A40A for ; Thu, 4 May 2006 14:30:19 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11AE743D95 for ; Thu, 4 May 2006 14:30:09 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 2A617291F7B; Thu, 4 May 2006 11:30:03 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61787-06; Thu, 4 May 2006 11:30:08 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id A3D78291BF5; Thu, 4 May 2006 11:30:02 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 7E4C349320; Thu, 4 May 2006 11:30:12 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 7D54749314; Thu, 4 May 2006 11:30:12 -0300 (ADT) Date: Thu, 4 May 2006 11:30:12 -0300 (ADT) From: "Marc G. Fournier" To: Rutger Bevaart In-Reply-To: Message-ID: <20060504112918.Q1147@ganymede.hub.org> References: <20060504070534.98F0216A432@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:30:24 -0000 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: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664