From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] test lab hw
Date: Wed, 11 May 2011 13:15:08 -0600 [thread overview]
Message-ID: <BANLkTinDSMo-A06OWZ=TwknxXaMNOBhkQQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
a 16+ port power switch like this would be great - In the future, several of
these would be good:
http://www.digital-loggers.com/vpdu.html
Sorry for not thinking about this earlier, hopefully you already have large
power strips, but this one has a scriptable web interface and is cheap
(179). Remote power cycling is good...
Cables. These routers come with one cable. Having an extra cable per router
allows WAY more ports to be hooked up.
Tape to mark the routers with identities that make sense.
As I sit in this nice, shiny, cool, office, surrounded by machines that
appear idle, I can't help
but want to turn one of them into a test server... or at least connect to
the outside world enough to get to galapagos on GigE (and preferably the
bismark database collector (is that d4? galapagos?)) No further outside
access is strictly needed (although I'd like to get to the package server,
too, which I assume will be d4 and the new box on the floor there))
Assumption: You don't have 16 real ips available, but using up 2-3 of what
you have here would probably be about right, if possible. Can they get to
this lab?
I was also curious if we could rope in a few offices of extra distances
around the building (connected as stations to the main set in the lab)...
I've already tested station mode and AP mode co-existence and it works
fairly well... they won't need ethernet access....
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next reply other threads:[~2011-05-11 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 19:15 Dave Taht [this message]
2011-05-11 19:38 ` Nick Feamster
2011-05-11 19:48 ` 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='BANLkTinDSMo-A06OWZ=TwknxXaMNOBhkQQ@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