From: Michael Boutte <maboutte@pacbell.net>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Building a Raw Bridge
Date: Sat, 11 Apr 2009 08:54:21 -0700 [thread overview]
Message-ID: <49E0BD2D.9030908@pacbell.net> (raw)
Hi All,
I think the little diagram of the circuit became a mess when
transmitted. How about this attempt? This is the hub of a hub and spoke
topology and there is normally only one transmit and multiple receivers
Here is what one end of the link looks like.
+-------------+
+ eth0 +---+ bridge 1 +---+ wan0 ---> Transmit
| +-------------+
|
switch--+
| +-------------+
+ eth0 +---+ bridge 2 +---+ wan0 <--- Receive
+-------------+
Mike Boutte
next reply other threads:[~2009-04-11 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 15:54 Michael Boutte [this message]
2009-04-13 16:56 ` [Bridge] Building a Raw Bridge Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2009-04-11 5:56 Michael Boutte
2009-04-13 17:59 ` richardvoigt
2009-04-13 23:32 ` Michael Boutte
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=49E0BD2D.9030908@pacbell.net \
--to=maboutte@pacbell.net \
--cc=bridge@lists.linux-foundation.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