Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Chris Lawrence <lordsutch@gmail.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Network behavior of Moca bridges
Date: Thu, 17 Apr 2014 13:03:02 -0700	[thread overview]
Message-ID: <CAA93jw5RT6kUAYNZjGyy-HTWvZEd3j4yHCAJqTP3oa8cVDfFuA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7VrFVYWADwM12nJ1DZ6pgQLoq03TSb_=e8hbdqHRQJgQ@mail.gmail.com>

Obviously my ascii art skills are in decline in an age when I don't know
when I have 72 chars to deal with. Trying the more complex topology
again:

 source 1                                   source 2
       |                                              |
  moca bridge  1                        moca bridge 2
                      \                        /
                       \                      /
                      shared moca cable
                                   |
                      moca device or bridges


Or your more classic:

 source 1                                   source 2
       |                                              |
  moca bridge  1                        moca bridge 2
                      \                        /
                       \                      /
                      shared moca cable
                       /                       \
                      /                         \
  moca bridge  3                        moca bridge 4
       |                                           |
     sink 5                                  sink 6

In my world the distinction between source and sink
is kind of vague as all traffic is bidirectional, whether that
be as basic as an ack, or a file being streamed elsewhere.

I am under the impression however that moca can receive
multicast video streams, which have no equivalent.

-- 
Dave Täht

      reply	other threads:[~2014-04-17 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 21:05 Dave Taht
2014-04-15 21:30 ` Aaron Wood
2014-04-16 11:58 ` Frits Riep
2014-04-17 19:09   ` Chris Lawrence
2014-04-17 19:48     ` Dave Taht
2014-04-17 20:03       ` Dave Taht [this message]

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=CAA93jw5RT6kUAYNZjGyy-HTWvZEd3j4yHCAJqTP3oa8cVDfFuA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=lordsutch@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