From owner-freebsd-net Sat Aug 31 0:58:59 2002 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D99437B400 for ; Sat, 31 Aug 2002 00:58:57 -0700 (PDT) Received: from quack.kfu.com (adsl-67-113-12-90.dsl.snfc21.pacbell.net [67.113.12.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6099743E42 for ; Sat, 31 Aug 2002 00:58:56 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [IPv6:3ffe:1200:301b:2:230:abff:fe06:62e5]) by quack.kfu.com (8.12.3/8.12.3) with ESMTP id g7V7wskb030491 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Sat, 31 Aug 2002 00:58:55 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com (localhost [127.0.0.1]) by icarus.kfu.com (8.12.5/8.12.5) with ESMTP id g7V7wnDw019558 for ; Sat, 31 Aug 2002 00:58:49 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Message-ID: <3D707738.6050805@quack.kfu.com> Date: Sat, 31 Aug 2002 00:58:48 -0700 From: Nick Sayer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1b) Gecko/20020727 X-Accept-Language: en, en-US, en-GB MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: IPv6 PPP - the real issues Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok. I sort of misunderstood the problem(s). The current behavior is this: 1. When you create a tun device, it ends up getting a non-p2p link-local address. This winds up confusing things because ppp will bring up a link-local p2p address pair, and outgoing packets wind up with the wrong source address. Deleting the spurious link-local address makes link-local connectivity work with Brian Somer's latest stuff. I believe that "auto_linklocal=1" is doing this. I suspect that that behavior is inappropriate for tunnel devices. 2. I can establish link-local connectivity just fine, but attempting to set up an rtadvd on the 'server' and and an rtsol on the 'client' end doesn't seem to do anything. I can run a tcpdump and see the router solicitations head upstream and the router advertisments in reply go downstream, but nothing ever gets added. If I'm not mistaken, the kernel is responsible for processing received router / prefix solicitations, right? So why isn't it processing these ones? 3. If I manually make up a /64 and set up an anycast alias for the 0 address (all-routers) and a manual route to that subnet on the tunnel device on the server, and manually add that prefix on the client, everything works correctly. The fact that I must add the prefixed address manually to the client is, I believe, more or less the last stumbling block. My goal is to document the process of setting up an IPv6 only dialup ISP. Customers would get a dynamic 64 bit prefix, which they could share with neighbor discovery proxying if they want. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message