From owner-freebsd-stable@FreeBSD.ORG Mon Nov 14 20:40:04 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 11FB916A434 for ; Mon, 14 Nov 2005 20:40:04 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9056143D49 for ; Mon, 14 Nov 2005 20:40:03 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: by xproxy.gmail.com with SMTP id t10so1744742wxc for ; Mon, 14 Nov 2005 12:40:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kAzs6Pcq22ZQG5/Q71WdV++2e8Nkgl7ln6CXhDrhsUSsYv9h/QKOJQ7jfgqy2UlDpi27bKT1KtQlBvz5KfAqIFROglQduk2yhaFz1VfXR5MawK24nzeasaZ6sbzE5ntXo8UEvkOqyL7GL1zZGxradKmT4zHkSy4ltTlKM7dv7CE= Received: by 10.65.83.18 with SMTP id k18mr4152580qbl; Mon, 14 Nov 2005 12:40:02 -0800 (PST) Received: by 10.65.150.7 with HTTP; Mon, 14 Nov 2005 12:40:02 -0800 (PST) Message-ID: <8eea04080511141240vb7f9f46wba4152490ec8809c@mail.gmail.com> Date: Mon, 14 Nov 2005 12:40:02 -0800 From: Jon Simola Sender: jsimola@gmail.com To: "Marc G. Fournier" In-Reply-To: <20051114162702.H1019@ganymede.hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051114162702.H1019@ganymede.hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: 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:40:04 -0000 On 11/14/05, Marc G. Fournier wrote: > There is a problem with the latest 4-STABLE where when you move an IP fro= m > 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 ... > Does anyone have a 'work around' for this? arp -s 10.0.2.3 00:00:10:20:30:45 pub On the "old" owner of the ip address, publish the MAC of the new owner (10.0.2.3 being the ip that was moved, 00:00:10:20:30:45 being the new MAC). I do this all the time as someone set this stupid Cisco switch up with a 2 hour ARP cache and I can't change/disable it. Once you verify that the router gets updated, delete the published arp entr= y. -- Jon Simola Systems Administrator ABC Communications