From owner-freebsd-stable@FreeBSD.ORG Tue Aug 12 11:02:44 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 4C674106564A; Tue, 12 Aug 2008 11:02:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 1292F8FC0C; Tue, 12 Aug 2008 11:02:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KSreE-000H0z-Oe; Tue, 12 Aug 2008 12:02:42 +0100 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KSreE-000ATd-NT; Tue, 12 Aug 2008 12:02:42 +0100 To: mat@FreeBSD.org, stable@freebsd.org In-Reply-To: <2D4221F0175C7261ECD00191@atuin.in.mat.cc> Message-Id: From: Pete French Date: Tue, 12 Aug 2008 12:02:42 +0100 Cc: Subject: Re: 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 11:02:44 -0000 > 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. What are your prefix lengths on the various interfaces, and does 2a01:678:100:2:: have a route back to 2a01:678:1:443::443 ? If you can show us the config on the interfaces of the three machines then we might be able to get a better idea. I am imagining how you have these three boxes connected in my head, but nothing beats an explanation plus the config :-) > 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 I've used all of those with IPv6 and they work fine, it's most likely a small config problem. I had a lot of frustrations with IPv6 when I started using it - though now it is working I wouldn't be without it. -pete.