From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] smoketesting capetown router testing
Date: Mon, 9 May 2011 09:54:59 -0600 [thread overview]
Message-ID: <BANLkTimOEPq_VALSy5NS8+1L1u4LVrc-Yw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
After a major hack session all of sunday, the "capetown" bismark router code
improved
by quite a bit.
Notably Travis Kemen made enormous improvements to the web interface, fixing
most of the known bugs, and Brian Poole got synced up and contributed a much
better than mine "time" package and made progress on more bismark packaging.
I can't remember what I did, personally, it's kind of blurry.
I've closed a few of the outstanding bugs on the roadmap, and would
certainly like some others to
try out the latest images available from:
http://huchra.bufferbloat.net/~bismark/capetown-wndr3700v2/ar71xx/
(it ran all night here with load tests)
While you can use the sysupgrade tool at this point it is best to do a
sysupgrade -n
and wipe out your existing configuration.
There are several more fixes in the queue for outstanding bugs but I hope we
can freeze on a "base" by tomorrow.
See roadmap and bug lists for more details (filter on "closed" to see what
got fixed)
http://www.bufferbloat.net/projects/uberwrt/roadmap
(please note that not everything is on the roadmap above)
Overall bug/feature list:
http://www.bufferbloat.net/projects/uberwrt/issues
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1684 bytes --]
reply other threads:[~2011-05-09 15:48 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimOEPq_VALSy5NS8+1L1u4LVrc-Yw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bismark-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