From: Nick Feamster <feamster@cc.gatech.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] assembling a testbed
Date: Mon, 9 May 2011 15:06:20 -0400 [thread overview]
Message-ID: <8A1A6689-270B-42F1-ABFB-B66A27A2CD66@cc.gatech.edu> (raw)
In-Reply-To: <BANLkTi=Ho06_a3bKcDyWQzFasySQTHagYQ@mail.gmail.com>
We have been working on getting them ASAP. Shipment was delayed for bureaucratic reasons. :-( But, we were in the purchasing office this morning, and hopefully we'll have them soon. Fallback plan is a shopping spree.
-Nick
On May 9, 2011, at 3:04 PM, Dave Taht wrote:
> I had rather hoped the wndr3700v2 routers would have arrived by now. Can you ping them to see if they will arrive in time? If not, acquiring sufficient routers for the trip is becoming rather important. I'd like to be testing by wednesday.
>
> Given that we had over 10% infant mortality on the 2.4Ghz radios, I worry. Also since the problem has been the same across multiple wndr3700s I figure it's a manufacturer switch/mac interface change that can be fixed (somehow), with a bit of work at the driver level (might require dissassembly, too)
>
> Lacking a testbed as such, I have been assembling the 3 nano-5 routers I have into a form that could be used to exercise the few wndr3700v2s we have. It would be good to coax as many people in the lab as possible to login via the testbed routers during the test period, as well.
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
next prev parent reply other threads:[~2011-05-09 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 19:04 Dave Taht
2011-05-09 19:06 ` Nick Feamster [this message]
2011-05-09 19:14 ` Dave Taht
2011-05-09 19:15 ` Nick Feamster
2011-05-09 22:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8A1A6689-270B-42F1-ABFB-B66A27A2CD66@cc.gatech.edu \
--to=feamster@cc.gatech.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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