Fantastic to hear about recent dhcpv6 developments!
I haven't had the time to use the tweaks advertised to make it working on
3.7.3-2 nor to test 3.7.4-3 but I found something else...

Since the last builds were about making ipv6 more usable I played with some
proxies.
I added this to /etc/hosts to see if things break:
::1 localhost localhost6

And they did just a bit. See, I configure my clients to talk to privoxy on
ipv4 (until I get Ipv6 for clients), port 8118, then I configure privoxy to
talk to polipo on localhost (router) on port 8123, so it's:

[client] ---> [privoxy on router:8118] ---> [polipo on router
localhost:8123]  ---> [WAN]

(side note: this is the recommended order of chaining these proxies, and so
TFO only gets used locally as privoxy does not have a TFO patch, I could
write a patch for that, but I never have the time to debug why my cero
builds always break :-( )

ANyway, this doesn't work (err: Refusing connection from unauthorised net)
because thanks to my modification to /etc/hosts, it talks to IPv6 localhost
(::1 instead 127.0.0.1) and /etc/config/polipo doesn't allow ::1 by current
config so I had to add this to /etc/config/polipo:
list 'allowedClients' '::1'
I'm not saying this is something that definitelly needs a change and it's
caused by my mods anyway, but I'm just saying ip6 naming or addressing will
potentially create a need to cater for them in various configs of various
apps.

(yes, it still breaks on dns after a while, but that's another story)

Anyway, Dave, I'm very happy with Cerowrt feature set; especially now that
we have DLNA/UPNP stuff sorted. (although I haven't tested ip6 support, I
will when I get clients using ip6 soon :-)

Best Regards,
Maciej

On Sun, Jan 27, 2013 at 1:09 PM, Dave Taht <dave.taht@gmail.com> wrote:

> thx  for the hard work of everybody here on straightening out the ipv6
> configuration issues!
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.4-3/
>
> + ipv6 traps dead, dead, dead
> + dnsmasq-2.66test12 with dhcpv6 (I hope!) by default
> + config for such
> + ntpclient/and luci app for such removed
> + ntp server enabled by default
> + nut (ups daemon) support added as a module (support for usbhid for
> cyberpower upses, which I just got 3 of)
>
> I *haven't tested this* however the delta from 3.7.4-2 is small (and it's
> 4AM, so the way things are going y'all will have found and fixed 2 more
> bugs before I wake up).
>
> Next up here from an ipv6 perspective is dhcpv6-pd, trying to come up with
> something that will work again for ahcp, and hopefully cisco's "pie"
> algorithm and a revised version of "cake"... at which point I'd like to
> think "beta", and regardless, start updating the web site to point to
> "modena" rather than "sugarland" as the release, updating the
> documentation, etc, etc.
>
> If anyone has any "must haves" before calling this release "feature
> complete", and ready for beta, speak up now!
>
> One thing waiting in the wings is a vmware vm of a complete ubuntu based
> cerowrt build system. It is kind of my hope to lower the barriers to entry
> to distribute that. I have that ready to go, I just don't have the
> bandwidth available right now to upload a 2GB file.....
>
> PS
>
> There's also up a version for the picostation 2mHP and nanostation 5M
> radios. This is a highly specialized build requiring babel and p2p links,
> it goes up on on a /32 only by default, has my public key in it, and a few
> other things. I'm at the yurtlab for a week and hope to test stuff at scale.
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/nano-m/3.7.4-3/
>
> back to bed.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>