From: Mike O'Dell <mo@ccr.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 31, Issue 4
Date: Sat, 07 Jun 2014 14:02:43 -0400 [thread overview]
Message-ID: <20140607180243.D681A119C54@ccr.org> (raw)
In-Reply-To: Your message of "Fri, 06 Jun 2014 09:09:54 PDT." <mailman.51111.1402070994.1815.cerowrt-devel@lists.bufferbloat.net>
excuse my naivete, but why on earth is homenet worried about
"interior routers"? there shouldn't *be* any interior routers
in a home network. ethernet switches, sure, but not routers.
-mo
next parent reply other threads:[~2014-06-07 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51111.1402070994.1815.cerowrt-devel@lists.bufferbloat.net>
2014-06-07 18:02 ` Mike O'Dell [this message]
2014-06-07 18:21 ` Dave Taht
2014-06-07 18:54 ` Mike O'Dell
2014-06-07 19:07 ` Dave Taht
2014-06-07 19:20 ` Mike O'Dell
2014-06-07 19:41 ` Dave Taht
2014-06-07 19:54 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140607180243.D681A119C54@ccr.org \
--to=mo@ccr.org \
--cc=cerowrt-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