Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Mike O'Dell" <mo@ccr.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 31, Issue 4
Date: Sat, 7 Jun 2014 11:21:17 -0700	[thread overview]
Message-ID: <CAA93jw6hhUiBfA+x68S52dcGs_vj8GJ_fyuBgev9=0NnTM-3bA@mail.gmail.com> (raw)
In-Reply-To: <20140607180243.D681A119C54@ccr.org>

The homenet argument, is that there is already typically dozens of
routing like devices in the home today, and
double/triple nat often resulting from misconfiguration.

Townsley makes the arguement coherently in the video I mentioned
earlier. If you can take 15 minutes out of your day to watch that,
perhaps the point will be made.

Notably bridging ethernet to zigbee and sensor networks (and wifi, to
a large extent) is an horrifically bad idea. (IMHO). There are people
strongly in favor of using Rbridges in that situation...

Short term, finding ways to avoid double-triple-nat would be an
improvement on how things work.

In my own case I worry more about small business than home networks.
Once you fall off the cliff of bridging,
the route towards routing is hard. And I'm totally in love with the
idea of getting multiple uplinks to different providers to "just
work".


On Sat, Jun 7, 2014 at 11:02 AM, Mike O'Dell <mo@ccr.org> wrote:
>
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-06-07 18:21 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
2014-06-07 18:21   ` Dave Taht [this message]
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='CAA93jw6hhUiBfA+x68S52dcGs_vj8GJ_fyuBgev9=0NnTM-3bA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mo@ccr.org \
    /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