From: david@lang.hm
To: bloat@lists.bufferbloat.net
Subject: [Bloat] what is ready for prime time?
Date: Tue, 22 Nov 2011 16:33:53 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1111221627410.10159@asgard.lang.hm> (raw)
I'm running the wireless network for SCALE in late January (~1800 people
with a 45Mb uplink), we will be using ~30 netgear WNDR3700v2 access points
running openwrt (or a derivitive). What of the stuff that is in CeroWRT is
considered reliable enough for production use like this? (I know that a
lot of stuff there is not)
Also, what would you folks like to have me put on the APs or network to
gather info under these harsh conditions?
last year we moved to a larger hotel and I ran fairly stock DD-WRT on the
same access points I had used the year before and things did not work very
well, but I think I ended up without having dense enough coverage so this
year I'm moving to openwrt (to give me more control) and doubling the
number of access points.
David Lang
next reply other threads:[~2011-11-23 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 0:33 david [this message]
2011-11-24 11:41 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1111221627410.10159@asgard.lang.hm \
--to=david@lang.hm \
--cc=bloat@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