From owner-freebsd-stable@FreeBSD.ORG Wed Apr 13 15:04:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C8C4106566C for ; Wed, 13 Apr 2011 15:04:41 +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 1C1738FC0A for ; Wed, 13 Apr 2011 15:04:40 +0000 (UTC) Received: from PWSVL-EXCHTS-01.internal.cacheflow.com ([10.2.2.122]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id p3DEq9Ju014099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Apr 2011 07:52:10 -0700 (PDT) Received: from PWSVL-EXCMBX-01.internal.cacheflow.com ([fe80::15bc:12e2:4676:340f]) by PWSVL-EXCHTS-01.internal.cacheflow.com ([fe80::5c50:e2ba:8115:4223%20]) with mapi id 14.01.0255.000; Wed, 13 Apr 2011 07:52:06 -0700 From: "Li, Qing" To: Pete French , "freebsd-stable@freebsd.org" Thread-Topic: IPv6 / ndp taking a long time to resolve in this weeks STABLE Thread-Index: AQHL+cOkKKZnKebT+ECqn4FQh7zGBZRb33zw Date: Wed, 13 Apr 2011 14:52:05 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.150.1.170] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: IPv6 / ndp taking a long time to resolve in this weeks STABLE 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: Wed, 13 Apr 2011 15:04:41 -0000 I haven't modified the ndp related code for quite a long time, but recently= have seen some postings regarding incomplete ndp entries (still catching up on emails= ). Changes committed in the past year or so were related to locking and memory= leak, not functional updates. I have seen this issue with ARP, where incoming ARP requests are not comple= ting the entries until an explicit outgoing packet is generated right after the system boots. Email me when you recreate the problem. --Qing > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Pete French > Sent: Wednesday, April 13, 2011 3:14 AM > To: freebsd-stable@freebsd.org > Subject: IPv6 / ndp taking a long time to resolve in this weeks STABLE >=20 > Following on from what I write about CARP, I've noticed another strange > thing happening with IPv6. Things which appear not to connect, and then > connect after a few seconds. To me it looks like ndp is having a > hard time mapping addresse to ether addresses. What I see is that > if a ping doesnt work and I look at the ndp, it has 'no entry' in > it for at least 5 seconds. Eventually it gets one, anbd thenm > everyhting > is fast as ever. But all a bit strange - ndp problems would epxlain > what I was seeing with CARP too. >=20 > Am going to try and set up a little test network here to experiment > with > this later today, in the meantime, has anyone else had IPv6 issues with > a recent stable ? >=20 > -pete. >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org"