Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Michael Boutte <maboutte@pacbell.net>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Building a Raw Bridge
Date: Mon, 13 Apr 2009 09:56:33 -0700	[thread overview]
Message-ID: <20090413095633.63894b2f@nehalam> (raw)
In-Reply-To: <49E0BD2D.9030908@pacbell.net>

On Sat, 11 Apr 2009 08:54:21 -0700
Michael Boutte <maboutte@pacbell.net> wrote:

> 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
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge

What you are doing is not really a bridge, so of course it
won't work.  If you need to glue devices together, and the
performance overhead isn't too high do it in user space.

  reply	other threads:[~2009-04-13 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 15:54 [Bridge] Building a Raw Bridge Michael Boutte
2009-04-13 16:56 ` Stephen Hemminger [this message]
  -- 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=20090413095633.63894b2f@nehalam \
    --to=shemminger@vyatta.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=maboutte@pacbell.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