Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cerowrt-3.10.32-9 released
Date: Sun, 16 Mar 2014 12:58:28 -0700	[thread overview]
Message-ID: <CAA93jw6o9cmw2=8Qjd=piaJDJjUqhDDfN1YiH=0KxrSQXHLHxQ@mail.gmail.com> (raw)

Get it at:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.32-9/

I've been running this a few days now with no problems.

+ resync with openwrt head
+ upnp (when enabled) works with a yamaha receiver, torrent, and a few
other things
+ with no ipv6, 0 unaligned instruction traps
+ Latest SQM code
+ Latest dnsmasq with dnssec enabled
+ everything rolled up from the comcast releases

- untested with ipv6 as yet
- haven't tried blue-ray
- My nexus-4 still fails to get an address at 5ghz (but felix's
succeeds) so I'm going to assume
there's something wrong with my nexus-4. A newer nexus-7 works
correctly. There were a ton
of noise rejection patches from openwrt head that made it into this release...
-

It looks like you can increase the dnsmasq cache to 9999 and improve
the hit rate
on the namebench test without impacting memory much. Not that
namebench is representative.
And various test sites for dnssec return green.

In other plus's: a whole bunch of vm boxes were donated by google and
after a bit of fiddling by travis yesterday the build cluster is in
the best shape I've ever seen it.

http://buildbot.openwrt.org:8010/buildslaves

It's my hope that by speeding up build cycle time this will make
openwrt head much more stable,
and thus cerowrt more stable, and speed up the pending barrier breaker
release of openwrt by a lot.

I have kind of taken 2 weeks off from cero and have to look at my
notes for what else is
a barrier to a stable release. As best I recall my last two wishlist
items were procd support
for babeld, and bcp38 support. We have issues still with upnp. hnetd,
and ohybridproxy are entirely untested, and I am fiddling with the
auto target/interval calculation with various methods.

Other stuff?

I am firing up a new ubnt build and giving an edgerouter build a shot.
With that stuff building
again I should be able to start bringing the yurtlab back online for
more extensive automated testing.

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

             reply	other threads:[~2014-03-16 19:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 19:58 Dave Taht [this message]
2014-03-16 21:27 ` Valdis.Kletnieks
2014-03-16 21:45   ` Dave Taht
2014-03-17  0:03     ` Toke Høiland-Jørgensen
2014-03-17  0:42     ` Valdis.Kletnieks
2014-03-17  0:54       ` Dave Taht
2014-03-17 12:20 ` Michael Richardson
2014-03-17 13:40   ` Dave Taht
2014-03-17 14:30     ` Toke Høiland-Jørgensen
2014-03-17 14:39       ` Toke Høiland-Jørgensen
2014-03-17 14:55       ` Dave Taht
2014-03-17 14:55     ` Michael Richardson
2014-03-17 15:18       ` Dave Taht
2014-03-18 10:00 ` Török Edwin
2014-03-18 12:12   ` Sebastian Moeller
2014-03-18 14:21     ` Dave Taht
2014-03-18 15:22       ` Török Edwin
2014-03-18 15:35         ` Dave Taht
2014-03-18 16:49           ` Török Edwin
2014-03-18 17:03             ` Dave Taht
2014-03-18 17:06           ` Valdis.Kletnieks

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='CAA93jw6o9cmw2=8Qjd=piaJDJjUqhDDfN1YiH=0KxrSQXHLHxQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.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