From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net, bloat-devel@lists.bufferbloat.net
Subject: [Bismark-devel] merging features from iscwrt into bismark
Date: Wed, 4 May 2011 11:55:33 -0600 [thread overview]
Message-ID: <BANLkTin+-7LAHRGjqge_dCm5fAsybjmdjA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
iscwrt is coming along nicely, and there are a few features in it that might
be worth making into bismark's capetown release.
Notably it has a real webserver (lighttpd), and python cgi support, as well
as a public/private SSID implementation and a decent set of pre-built
firewall rules. We have plenty of flash and memory left over with the
installed tools and daemons I'm aware of right now.
I don't regard iscwrt's core features (bind9 + isc dhcpd) as ready for prime
time as yet, the core blocker is no web interface on that. It would be nice
to get dnssec tested in the field at some point but not as part of the
capetown release.
Somewhat related to this is the idea of spreading next week's testing across
the bloat userbase. I daresay we could pick up 10+ testers if we talk about
what we need to the bloat mailing list....
I regard adding the buffalo router to the testing list as a big risk (will
it work at all?) that also mitigates another big risk - that the heat
management on the existing wndr won't stand up to the rigors of elsewhere -
the buffalo should run mildly cooler with only one radio installed (and may
have better antennas)
thoughts?
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1404 bytes --]
reply other threads:[~2011-05-04 17:51 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=BANLkTin+-7LAHRGjqge_dCm5fAsybjmdjA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=bloat-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