From owner-freebsd-stable@FreeBSD.ORG Thu May 4 13:07:04 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 DC78F16A401 for ; Thu, 4 May 2006 13:07:04 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53BEC43D45 for ; Thu, 4 May 2006 13:07:03 +0000 (GMT) (envelope-from fbsd-stable@mawer.org) Received: from [127.0.0.1] (c220-237-120-88.thorn1.nsw.optusnet.com.au [220.237.120.88]) by mail08.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k44D70Ip016326; Thu, 4 May 2006 23:07:02 +1000 Message-ID: <4459FC7A.7040807@mawer.org> Date: Thu, 04 May 2006 23:07:06 +1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Rutger Bevaart References: <20060504070534.98F0216A432@hub.freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 13:07:04 -0000 On 4/05/2006 6:20 PM, 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). > 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. If true, this would explain something I've seen this a couple of times when an IP address has changed, and the ARP cache on the router had to be flushed before the new address was picked up correctly. In all cases this was running on machines with em0 (Intel Pro/1000) NICs. I hadn't thought too much of it at the time as it was not a frequent occurrence and thus I put it down to one of those things that "just happens". -Antony