What you described is a different interface for tx and rx. What you've
drawn is separate tx and rx radios which are melded in the driver and expose
a single interface "wan0". Which is it? (If the drawing is correct,
I
don't think you have a problem at all, aside from trying to use two bridges
when you need only one)
On Sat, Apr 11, 2009 at 12:56 AM, Michael Boutte <maboutte at
pacbell.net>wrote:
> 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
>
> _______________________________________________
> Bridge mailing list
> Bridge at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.linux-foundation.org/pipermail/bridge/attachments/20090413/c12f4902/attachment.htm