On Mon, Apr 23, 2012 at 11:43 AM, David Woodhouse <dw...@infradead.org> wrote: > On Mon, 2012-04-23 at 20:14 +0200, Gert Doering wrote: >> (Now, what I'm not sure whether OpenWRT already has this: to fully >> utilize IPv6 over here, what you need to have is dynamic IPv6 prefix >> support using DHCP-PD. As in "router queries ISP for a prefix, ISP >> assigns 2001:db8:1::/56, router assigns 2001:db8:1:1::/64 to LAN, >> 2001:db8:1:2::/64 for WiFi and informs radvd that this is the prefix >> to be used". AVM's Fritz!Box does this nicely today, but not with >> open source components...) > > It's documented here: http://wiki.openwrt.org/doc/uci/dhcp6c > > I haven't actually tried it; I have to manually configure the range of > Legacy IP addresses anyway, so it's easy enough to configure the IPv6 > too. But I *will* try it, and make sure it interoperates with my ISP > correctly.
It has long been a goal of mine to have both cerowrt and openwrt builds ready for world ipv6 launch day and be able to fully meet this spec: http://www.worldipv6launch.org/form/?q=3 I'd like to think I'm close. But truly getting there will require more folk to want to do it, by that date. Please goferit! All the machines in the bloatlab are native dual-stack (see, for example, http://europa.lab.bufferbloat.net/cerowrt/ ), and I have several running dhcp-pd, sorta. It's my last remaining bug. I tried dibbler (crashes after 24 hrs), and isc-dhcp (too big, too complex) and have fallen back to wide. I have reports of it working in New Zealand. The biggest problem that I have (in America, at least) is that comcast's first rollout is only going to be a single /64 delegation, which breaks cerowrt's multiple interface scheme, but will hopefully work ok with openwrt. Still, /64 only is crazy and I'm told they intend to do better by fall. Certainly other providers are handing out /56s and /60s. > We should make sure it's enabled by default. Latest build for me, wide-dhcpv6 is installed but not enabled by default. After some testing, it will. > There should be no need for anyone to disable IPv6, except perhaps if > they mean by that "turn off automatic 6to4". If they're stuck in the > 20th century and don't have IPv6 routing, they won't get IPv6. What's to > disable? > > (And no, I wouldn't advocate 6to4 being enabled by default anyway). I had it enabled by default during comcast's trials. It worked great, on their network (and having a /48 was good too). It didn't work very well elsewhere, so it's in there, but disabled by default. I also have HE tunnels and 6rd working. I'm more of the opinion that ipv6 needs to be made to work, using every method possible, and if possible, those methods should be able to co-exist, using policy routing. That proves to be hard. > > -- > dwmw2 > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > -- Dave Täht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
