From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from chi.subsignal.org (cxd-2-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:ed::2]) by huchra.bufferbloat.net (Postfix) with ESMTP id AC86C21F17D for ; Wed, 12 Dec 2012 01:19:54 -0800 (PST) Received: from [192.168.178.21] (unknown [212.255.230.88]) by chi.subsignal.org (Postfix) with ESMTPSA id 7A569126176; Wed, 12 Dec 2012 10:20:16 +0100 (CET) Message-ID: <50C84C38.7040207@openwrt.org> Date: Wed, 12 Dec 2012 10:19:52 +0100 From: Steven Barth User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ole_Tr=F8an?= References: <8F973FF7-B39D-4E21-B889-14F6105A29F4@employees.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Current state of ipv6 in openwrt barrier breaker X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2012 09:19:55 -0000 Hi Ole, Dave, > the worst you can expect is a /64 on the link-net and no PD. I suggest you don't support that case. The problem is that (some) people are expecting to be able to just plug other routers behind their main uplink router for whatever reasons (e.g. additional WiFi-network etc.) like they have with IPv4 or e.g. make a router just connect to a non-WDS WiFi in client mode and extend their network. As the home router shouldn't do PD to further distribute the ISP-prefix it is hard to support this with IPv6 except with detecting the case and doing NDP-Proxying then as bridging might not always be possible or desired in this case. And supporting all of this above would have the side-effect that such ISP without PD would be supported as well so I'm not really sure.