From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] CeroWrt 3.6.11-2 is out with ipv6-support package, bleeding edge dnsmasq, upnp,
Date: Sun, 23 Dec 2012 21:41:35 +0100 [thread overview]
Message-ID: <CAMZR1YAXfwMLCicCLgnz4Pb8L2h=OKRPTFjThABc4UMMYo8eiQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4e4H7ispcStN3hPfCb7SmXqHKZ4Sg3c2Yv_YpL3bjEog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
Fantastic! I'll test the build with a upnp client and an ssdp device mid
next week.
Happy holidays!
Maciej
On 23 Dec 2012 21:08, "Dave Taht" <dave.taht@gmail.com> wrote:
> I am not in a position to test this release at all - I gave my last
> wndr3800s to a deserving student in Paris, and the only other ones I
> have are in the yurtlab and I'm 3000 miles from there.
>
> So do not under any circumstances install this one on your default
> gateway as yet.
>
> If you are daring, and bold, and have had perhaps a bit too much
> eggnog, please feel free to try out this release.
>
> I AM happy to announce that thx to stephen walker polishing up the
> last bits of bug http://www.bufferbloat.net/issues/362 and then
> getting them into ceropackages, that at least in theory we have
> working upnp and mini-dnssd support. I don't have a device that uses
> this stuff, so I'd like to know if they work, particularly on an xbox.
> Or if I still missed something... I would certainly like more people's
> xboxes working by christmas.
>
> There is also the first version of Steven Barth's new ipv6-support
> package - supporting 6in4, 6to4, 6rd, and native ipv6, AND *dhcp-pd*,
> interfacing with a totally bleeding edge and highly beta version of
> Simon Kelley's dnsmasq, which does saner ipv6 naming of slaac and
> dhcpv6 assigned names, and dnsmasq also does dhcp-v6 services, and
> handles RA announcements, in addition to it's also eminent duties as a
> dns and dhcp server.
>
> Expect bugs! but aside from some new fq_codel work and getting npt66
> to work this is rather close to "Feature complete" for the next stable
> version of cerowrt...
>
> And... radvd is DEAD. Yea!
>
> The ipv6-support package is rather under documented as yet, as you
> might imagine. The GUI needs updating... the new options to it and
> dnsmasq I have in my mailbox...
>
>
>
> --
> 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
>
[-- Attachment #2: Type: text/html, Size: 2876 bytes --]
next prev parent reply other threads:[~2012-12-23 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 20:08 Dave Taht
2012-12-23 20:09 ` Dave Taht
2012-12-23 20:29 ` Dave Taht
2012-12-23 20:41 ` Maciej Soltysiak [this message]
2012-12-23 22:31 ` Dave Taht
[not found] <mailman.2.1356379202.14075.cerowrt-devel@lists.bufferbloat.net>
2012-12-26 15:50 ` Richard Brown
[not found] ` <CAA93jw4X_=6O2Pnwk1wX+bKXGQHeUXrE3DGj1sAtPL_dUMQO1A@mail.gmail.com>
2012-12-26 16:26 ` Dave Taht
2012-12-26 16:34 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMZR1YAXfwMLCicCLgnz4Pb8L2h=OKRPTFjThABc4UMMYo8eiQ@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox