From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 01:13:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF962106566B; Thu, 15 Oct 2009 01:13:44 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D61E88FC1A; Thu, 15 Oct 2009 01:13:44 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n9F1DiO9000091; Wed, 14 Oct 2009 18:13:44 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Oct 2009 18:12:41 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ARP Changes Thread-Index: AcpNNJf6RjDjdETRRwma32MIH3lQ0Q== From: "Li, Qing" To: , Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: ARP Changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 01:13:45 -0000 > > I know that arp has changed a lot in FreeBSD 8. I am wondering if one > change was by design? In older versions of FreeBSD, if you ping a = host > that is on a local network but is down, after a few seconds ping = displays: > ping: sendto: Host is down > ping: sendto: Host is down > This turned out to be a regression bug. A wrong variable is used and the incomplete entry was timing out too fast. So the ARP probe = continues indefinitely ... =20 > > Using arp to display the arp table shows: > > host.domain (x.x.x.x) at (incomplete) on em0 [ethernet] I wasn't returning incomplete entries, but now I am ... I have a patch for both issues, but I need to clean up the code because that wrong variable is used elsewhere in the same module. I should be able to commit a permanent fix by tomorrow. -- Qing