From: Dave Taht <dave.taht@gmail.com>
To: David Lang <david@lang.hm>
Cc: Frank Horowitz <frank@horow.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Just FYI: WNDR3700 (v2???) refurbs available on Amazon for USD49.99
Date: Fri, 27 Feb 2015 19:27:14 -0800 [thread overview]
Message-ID: <CAA93jw49Ca7f-HLq8QZRq-Y0WN2aM05gXsxGpK12boBFdaE3uA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502271806250.20700@nftneq.ynat.uz>
On Fri, Feb 27, 2015 at 6:07 PM, David Lang <david@lang.hm> wrote:
> On Thu, 26 Feb 2015, Dave Taht wrote:
>
>> We will hopefully get around to a cerowrt refresh fairly soon - as
>> soon as some more test code lands - and do it on several platforms.
>> Until then, try chaos calmer - and for all I know we will end up
>> building more on openwrt directly this time rather than repeating all
>> the stuff that openwrt won't take upstream that is presently in
>> cerowrt.
>
>
> you may have posted this and I'm just not remembering, but do you have a
> list of what's in CeroWRT that OpenWRT won't take upstream (and any info on
> why they won't take the items)?
>
> Daivd Lang
* Unbridged interfaces - routing only
* Device Naming by function rather than type
* More open to ipv6 firewall
* Firewall using device pattern matching to avoid O(n) complexities in
firewall rules
* Babels on and preconfigured by default
* Oddball IP address range and /27 subnets
* Polipo Web proxy
* Samba by default
* Faster web server
* Weird port for the configuration web server
* Pre-enabled wifi and wifi mesh interfaces
* Huge amount of alternate qdiscs (like pie, ns2_codel, cake, cake2, etc)
And:
A build that includes all these things by default.
I note there are a couple nice "super-duper" builders of openwrt that
have WAY more features that ever made it into cerowrt. Although I
forget their names, they have their advocates on the openwrt forums.
(and both include sqm)
I have long meant to eval those and maybe hope to convince them to be
the next buildmaster for this project - the day to day grind of doing
a build, testing it, etc, was killing me - and y'all. Much better to
have it get filtered through someone else.....
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
next prev parent reply other threads:[~2015-02-28 3:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 18:15 Frank Horowitz
2015-02-26 18:44 ` Dave Taht
2015-02-28 2:07 ` David Lang
2015-02-28 3:27 ` Dave Taht [this message]
2015-02-28 4:44 ` David Lang
2015-02-28 15:25 ` [Cerowrt-devel] CeroWrt bits not in OpenWrt (renamed thread) Rich Brown
2015-02-28 16:47 ` Dave Taht
2015-02-28 21:41 ` David Lang
2015-02-28 23:58 ` David Lang
2015-03-12 16:43 ` Rich Brown
2015-03-12 20:31 ` Alan Jenkins
2015-03-12 20:43 ` Alan Jenkins
2015-03-12 21:21 ` Dave Taht
2015-03-13 0:53 ` Alan Jenkins
2015-03-13 15:00 ` Rich Brown
2015-03-12 21:47 ` Toke Høiland-Jørgensen
2015-03-12 21:59 ` Dave Taht
2015-03-13 15:26 ` Sebastian Moeller
2015-03-13 0:50 ` Alan Jenkins
2015-03-13 0:55 ` Sebastian Moeller
2015-03-13 1:35 ` David Lang
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=CAA93jw49Ca7f-HLq8QZRq-Y0WN2aM05gXsxGpK12boBFdaE3uA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=frank@horow.net \
/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