From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net, Colin McGregor <colin.mc151@gmail.com>
Subject: [Bloat] How soon can the brave but foolish start being early adopters
Date: Mon, 20 Feb 2012 10:05:42 -0500 [thread overview]
Message-ID: <4F426146.3010200@rogers.com> (raw)
I'm an interested lurker (and capacity planner) who might easily try
out the work that's been done in CeroWrt if it would be useful to you.
Consider me a prospective exposure tester (:-))
At the same time, I'm constrained to follow the very pedestrian
requirement of my provider, so I'm stuck running NAT. I know you're not
using NAT during the development, but I wonder if I can use it under
CeroWrt for my home network without messing anything up.
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
(416) 223-8968
next reply other threads:[~2012-02-20 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 15:05 David Collier-Brown [this message]
2012-02-21 0:30 ` Jim Reisert AD1C
2012-02-21 4:01 ` 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=4F426146.3010200@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=colin.mc151@gmail.com \
--cc=davecb@spamcop.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