From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 6058621F11C for ; Sun, 27 Jan 2013 14:12:42 -0800 (PST) Received: by mail-oa0-f43.google.com with SMTP id k7so575474oag.2 for ; Sun, 27 Jan 2013 14:12:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=jdMeQmpwNR4xuVS40fyEnSjnVpLUBwCHSiKG6JmJx8k=; b=i4Wj9VfqMyoe1N+kSierNR9qNqa1eYyXrXiSNc97FkCUxOmp9bcj8EMMYTGxuIBNZX CFhfvo4f93vnQgxd+PNCawx4DaazwYRLViWYElF9UJGMweGmaC4XdidJWbRVcQbrbdlp Mf9G0EBYr6Wd2DxadMsRZHKpXXTae+sR+Mv0xRn32dVxNRAxbefr/vEMZF1MG5dpMJKI quhEKEe4TIGPeXDTzo5LJ6gVCGoPaOkdFQUXY5W2UV8VK2qmqwqDXfZYNF/wO291uhsU BCs48ggamDXZi+XcsRC5P1LDcJxKp3jNVPsZZtrb9BfQyORAXJWJxbpHUzSA09WBz2Yj S18Q== MIME-Version: 1.0 X-Received: by 10.60.169.41 with SMTP id ab9mr9487596oec.58.1359324761294; Sun, 27 Jan 2013 14:12:41 -0800 (PST) Received: by 10.76.80.99 with HTTP; Sun, 27 Jan 2013 14:12:40 -0800 (PST) X-Originating-IP: [2001:470:70:31e::2] In-Reply-To: References: Date: Sun, 27 Jan 2013 23:12:40 +0100 Message-ID: From: Maciej Soltysiak To: Dave Taht Content-Type: multipart/alternative; boundary=bcaec54b4ff28808a104d44c7533 X-Gm-Message-State: ALoCoQnbYCyfPYoK2rAe0j1Gf0WLa1vaoE8AzZfU7bC5TcAcNQCdVIVKXll+Ri3RF9AQx9NbDXzh Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] cerowrt-3.7.4-3 released 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: Sun, 27 Jan 2013 22:12:42 -0000 --bcaec54b4ff28808a104d44c7533 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 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 wit= h > 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 entr= y > 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 fe= w > other things. I'm at the yurtlab for a week and hope to test stuff at sca= le. > > http://snapon.lab.bufferbloat.net/~cero2/cerowrt/nano-m/3.7.4-3/ > > back to bed. > > -- > Dave T=C3=A4ht > > 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 > > --bcaec54b4ff28808a104d44c7533 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Fantastic to hear about recent dhcpv6 developments!
I haven&= #39;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...
=C2=A0
=
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
=C2=A0
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 o= n localhost (router) on port 8123, so it's:
=C2=A0
[client] ---> [privoxy on router:8118] ---> [po= lipo on router localhost:8123]=C2=A0 ---> [WAN]
=C2=A0
(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 coul= d write a patch for that, but I never have the time to debug why my cero bu= ilds always break :-( )
=C2=A0
ANyway, this doesn't work (err: Refusing connecti= on 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 d= oesn'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 cause= d 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 a= pps.
=C2=A0
(yes, it still breaks on dns after a while, but that&= #39;s another story)
=C2=A0
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 clie= nts using ip6 soon :-)
=C2=A0
Best Regards,
Maciej
=C2=A0
=
On Sun, Jan 27, 2013 at 1:09 PM, Dave Taht <d= ave.taht@gmail.com> wrote:
thx=C2=A0 for the hard work of everybody here on straighte= ning 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 ho= pe!) by default
+ config for such
+ ntpclient/and luci app for such r= emoved
+ ntp server enabled by default
+ nut (ups daemon) support add= ed 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 (an= d it's 4AM, so the way things are going y'all will have found and f= ixed 2 more bugs before I wake up).

Next up here from an ipv6 persp= ective 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 "m= odena" rather than "sugarland" as the release, updating the = documentation, etc, etc.

If anyone has any "must haves" before calling this release &q= uot;feature complete", and ready for beta, speak up now!

One th= ing 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 distr= ibute that. I have that ready to go, I just don't have the bandwidth av= ailable right now to upload a 2GB file.....

PS

There's also up a version for the picostation 2mHP and na= nostation 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 tes= t stuff at scale.

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/na= no-m/3.7.4-3/

back to bed.<= font color=3D"#888888">

--
Dave T=C3=A4ht

Fixing bufferbloat with cerowrt: http:= //www.teklibre.com/cerowrt/subscribe.html=20
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel


--bcaec54b4ff28808a104d44c7533--