[Bridge] supporting a bridge-router configuration

Wayback MachineAbout this captureCOLLECTED BY Organization: Alexa Crawls Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period. Collection: Alexa Crawls DD Crawl data donated by Alexa Internet. This data is currently not publicly accessible TIMESTAMPSloadingLennert Buytenhekbuytenh@gnu.org
Wed, 19 Apr 2000 04:18:10 +0200 (MEST)On Tue, 11 Apr 2000, Jim Chapman wrote:> Is any work being done to support a “bridge-router” configuration? What> I mean by bridge-router is a box that routes any protocol that it knows> how to route, and bridges anything else, assuming bridging is enabled.I’ve got the netfilter plans as good as thought out now. Not carried outyet though.> [snip]> [snip]> Do we need a similar per-protocol enable/disable configuration to> control bridge forwarding in the new bridging code in order to support a> bridge-router configuration? Perhaps it could be a compile-time option> via another config parameter so that bridging-only configurations would> work just as they do now?There is a huge demand for packet type as well as MAC address filtering…I think we’d best do a full MAC addr netfilter infrastructure. Withinput/output chains for the ethernet layer, and forward chain for thebridge layer. The forward chain would have three possible verdicts: drop,’accept’, bridge. On drop, we drop it, on forward, we return it to net_bh,on bridge we steal it and bridge it ourselves. Sounds sane?Lennert