From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt-3.7.2-1
Date: Sat, 12 Jan 2013 13:55:41 -0500 [thread overview]
Message-ID: <CAA93jw6mX_Psvmwv-jFCMskBOUd82kP99Tw6q76VTRREj9=k3A@mail.gmail.com> (raw)
I lost half of last week to meetings, the other half to updating the
yurtlab and spent the remaining half updating stuff.
I now have a reasonably instrumented real-world, live test of the
nfq_codel and ceroshaper code, with with dozens to hundreds of users,
running through the donated vyatta box (and quite a few cerowrt,
nanostation m5s and picostations, and more legacy equipment that I
care to think about. I'm extremely happy about that.
3.7.2-.1 is at:
http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.2-1/
* Merge with openwork head
* Updated to Linux 3.7.2
* Added (hopefully) dpreed's needed modules for the LTE test
* Dnsmasq 2.66test8
* Small update to netperf
* No work on the TFO bug (
* No ipv6 nat
* Tagged and pushed out to cerowrt-next and cerofiles-next on github
I don't actually see a huge reason for anyone to upgrade to this, to
me getting the ipv6 nat stuff up and the TFO bug looked at would be a
reason to upgrade to a future release.
(what I mostly deployed was 3.7.1 based)
A multitude of bugs have crept into the nano-m build - notably the old
poe script no longer works and for some reason the wifi doesn't come
up on an IP address. I'm not keeping up with the ongoing netifd and
ipv6-support work on that front.... anyway, that build is rather
"special", and requires babel to find the device in the first place.
http://snapon.lab.bufferbloat.net/~cero2/cerowrt/nano-m/3.7.2-1/ (the
nano-m build applies to
Lastly:
I've had several requests to build a virtual of cero for some gui
work, those builds continue to fail to boot.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2013-01-12 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw6mX_Psvmwv-jFCMskBOUd82kP99Tw6q76VTRREj9=k3A@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