Ethernet Bridge development
 help / color / mirror / Atom feed
From: Michael Boutte <maboutte@pacbell.net>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Building a Raw Bridge
Date: Fri, 10 Apr 2009 22:56:56 -0700	[thread overview]
Message-ID: <49E03128.7080902@pacbell.net> (raw)

I'm having trouble figuring out how to make a bridge that does not block 
forwarding of packets when there is no receive channel in the same 
bridge. The reason I want to do this is that the return path is via 
another circuit. The two directions are on two different radios. I would 
think this would be like the response given to someone in July 2007 
about setting a "hub" mode by setting the aging timer to 0. I tried that 
and it did not work.

I also tried a few schemes with ebtables without success either. Is 
there some relatively easy way to make the bridge forward everything and 
not cut off the transmit after a single packet?

/ Here is what one end of the link looks like.
//
//                   +-------------+
// ///      /// + eth0 +---+   bridge 1  +---+ wan0 ---> Transmit
//        |          +-------------+ 
//        |                          
//switch--+                          
//        |          +-------------+ 
//        + eth0 +---+   bridge 2  +---+ wan0 <--- Receive
//                   +-------------+
/
The WAN side uses a synchronous serial interface to the radios for 
satellite communications. The other end uses a single radio and bridge.

Mike Boutte


             reply	other threads:[~2009-04-11  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11  5:56 Michael Boutte [this message]
2009-04-13 17:59 ` [Bridge] Building a Raw Bridge richardvoigt
2009-04-13 23:32   ` Michael Boutte
  -- strict thread matches above, loose matches on Subject: below --
2009-04-11 15:54 Michael Boutte
2009-04-13 16:56 ` Stephen Hemminger

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=49E03128.7080902@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