From owner-freebsd-stable@FreeBSD.ORG Mon Nov 14 20:28:57 2005 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 9A6B016A420 for ; Mon, 14 Nov 2005 20:28:57 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF3E343D55 for ; Mon, 14 Nov 2005 20:28:52 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 53E61C08BE9 for ; Tue, 15 Nov 2005 00:33:11 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41016-08 for ; Mon, 14 Nov 2005 20:28:48 +0000 (GMT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id BA51EC08BE0 for ; Tue, 15 Nov 2005 00:33:10 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 48A234AA39; Mon, 14 Nov 2005 16:28:52 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 40E3B4A951 for ; Mon, 14 Nov 2005 16:28:52 -0400 (AST) Date: Mon, 14 Nov 2005 16:28:52 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20051114162702.H1019@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: em devices not sending proper arp packets ... 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: Mon, 14 Nov 2005 20:28:57 -0000 There is a problem with the latest 4-STABLE where when you move an IP from one server on the network to a new one, a proper arp packet isn't being sent upstream, so the router isn't getting the change ... It only appears to affect the new em driver, as I have other servers on the network running an older kernel, where this doesn't happen ... Does anyone have a 'work around' for this? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664