From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] that latest build I did is looking good
Date: Thu, 25 Jun 2015 22:15:51 +0200 [thread overview]
Message-ID: <5CB152A1-53AC-458F-A73B-673626D0829D@gmx.de> (raw)
In-Reply-To: <CAA93jw7X2k+XMHwEzmHcx0c8kpv2X+rZDvJ1kf4fXprG=yrTyw@mail.gmail.com>
Hi Dave,
this looks really great, thanks a lot. As I want to take part in the cake party, this looks like the easiest/best way to start.
On Jun 25, 2015, at 19:34 , Dave Taht <dave.taht@gmail.com> wrote:
> I have been abusing it on a picostation and nanostation now for 48
> hours. The archer c7v2 (as a source specific gateway) for a week. A
> couple wndr3800s. No crashes. Can still trigger the dreaded wifi TX
> DMA bug, but it seems harder now. DID regularly crash the iwl in one
> box. [3]
>
> My mission was to get to something that I could deploy here at a small
> scale and just let run for a month while away in the eu, and that was
> looking dicy there for a while. (I am glad to have basically started
> in april!)
>
> So... we do, finally, have an openwrt build that uses cake, has the
> minstrel-blues patches, and andrews minimum variance patches, working
> dnssec (we hope!), and a new version of babel with ecn enabled, has
> snmp, that does dhcp-pd fairly right, and works with comcast. I also
> have things (odhcp6c is way better than isc, dibbler, wide) working
> fairly well with another debian based firewall.
>
> If/when new cake or sqm stuff arrives my plan (barring other major
> bugs elsewhere) is to just incrementally build that and tc-adv out of
> the above frozen repo. [1]
Question: sqm is from the openwrt repository or from ceropackages-3.10? I ask as the latest changes are only in ceropackages 3.10, since they certainly require testing before being inflicted on the openwrt crowd…
Best Regards
Sebastian
>
> --
> Dave Täht
> worldwide bufferbloat report:
> http://www.dslreports.com/speedtest/results/bufferbloat
> And:
> What will it take to vastly improve wifi for everyone?
> https://plus.google.com/u/0/explore/makewififast
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-06-25 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 17:34 Dave Taht
2015-06-25 20:15 ` Sebastian Moeller [this message]
2015-06-25 22:26 ` Dave Taht
2015-06-26 10:03 ` Sebastian Moeller
2015-06-26 13:53 ` Joel Wirāmu Pauling
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=5CB152A1-53AC-458F-A73B-673626D0829D@gmx.de \
--to=moeller0@gmx.de \
--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