From owner-freebsd-stable@FreeBSD.ORG Tue Aug 12 08:13:21 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EB061065672 for ; Tue, 12 Aug 2008 08:13:21 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [79.143.240.136]) by mx1.freebsd.org (Postfix) with ESMTP id 552538FC0A for ; Tue, 12 Aug 2008 08:13:21 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from atuin.in.mat.cc (ATuin.in.mat.cc [79.143.241.205]) by plouf.absolight.net (Postfix) with ESMTP id 1EEEC764007 for ; Tue, 12 Aug 2008 09:45:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id 82E7472EAE1 for ; Tue, 12 Aug 2008 09:45:50 +0200 (CEST) Date: Tue, 12 Aug 2008 09:45:48 +0200 From: Mathieu Arnold To: stable@freebsd.org Message-ID: <2D4221F0175C7261ECD00191@atuin.in.mat.cc> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========24C7F403A71FEEAD9299==========" Cc: Subject: neighbor discovery problem 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: Tue, 12 Aug 2008 08:13:21 -0000 --==========24C7F403A71FEEAD9299========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Since I added IPv6 to my network, and started really using it, I'm seeing some strange things happening. For instance, I'm on machine 2a01:678:1:443::443, and I do : $ traceroute6 -n 2a01:678:100:2:: traceroute6 to 2a01:678:100:2:: (2a01:678:100:2::) from 2a01:678:1:443::443, 64 hops max, 12 byte packets 1 2a01:678:1:443:: 0.636 ms 0.602 ms 0.525 ms 2 2a01:678:1:443:: 2999.665 ms !A 2999.636 ms !A 2999.680 ms !A 2a01:678:1:443:: is it's default gateway, and is also directly connected to 2a01:678:100:2::, but it does not seem to be able to contact it. If I log onto the gateway, and I : $ ping6 -c 1 2a01:678:100:2:: PING6(56=40+8+8 bytes) 2a01:678:100:: --> 2a01:678:100:2:: 16 bytes from 2a01:678:100:2::, icmp_seq=0 hlim=64 time=1.146 ms --- 2a01:678:100:2:: ping6 statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.146/1.146/1.146/0.000 ms It works, and now, I can : $ traceroute6 -n 2a01:678:100:2:: traceroute6 to 2a01:678:100:2:: (2a01:678:100:2::) from 2a01:678:1:443::443, 64 hops max, 12 byte packets 1 2a01:678:1:443:: 0.647 ms 0.671 ms 0.417 ms 2 2a01:678:100:2:: 0.852 ms 0.790 ms 0.669 ms Maybe I'm doing something wrong, but, well, I can't seem to find ou what. 2a01:678:1:443::443 is a 7.0 2a01:678:1:443:: is a 6.2 2a01:678:100:2:: is a 6.0 Those are not up to date to the latest thing you can get, but they're production machines, and I'm not really willing to upgrade them unless I really need to :-) -- Mathieu Arnold --==========24C7F403A71FEEAD9299========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkihP60ACgkQJqR8av5thQ88ZwCgmBVmDbQz5DfXtJQr3EhoQjiO 2q4An1mt0Em7cBfOEueELq7k4WARh6Fl =Z5dv -----END PGP SIGNATURE----- --==========24C7F403A71FEEAD9299==========--