Richard, The diagram may be deceiving. The real physical hardware consists of a separate embedded computer that is part of each radio. Each has an Ethernet port (eth0) and a synchronous hdlc port (wan0) and part of its purpose is to translate between the two mediums. In this one network configuration we want to use one radio to transmit to all remotes and one radio receive for each incoming signal from the remotes. At the hub site all of the radios with their embedded Linux computers would most likely be fed by a single switch. I can make this work setting each of the embedded computers as a router, but the configuration of all of the units and computers at the remote sites becomes significantly more complex than using a bridge, and requires changes each time the network is changed. A pseudo "raw" bridge would be ideal because it is then almost plug and play. I also don't need to worry about filtering the packets because there is a separate device before the bridge/radio that handle routing and other processing. I was simply hoping that there was some relatively easy method setting this up, perhaps with ebtables, that had the benefits of bridging without the complexity of routing. Mike Boutte richardvoigt@xxxxxxxxx wrote: > 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@xxxxxxxxxxx > <mailto:maboutte@xxxxxxxxxxx>> 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@xxxxxxxxxxxxxxxxxxxxxxxxxx > <mailto:Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx> > https://lists.linux-foundation.org/mailman/listinfo/bridge > > _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
