On Fri, Sep 5, 2008 at 4:16 AM, Alexander Dupuy <[EMAIL PROTECTED]> wrote: > If the only purpose of the bridge devices is to "hold IP configuration" for > enslaved physical interfaces (and not to provide layer-2 bridging between > e.g. different mesh channels so that broadcast / discovery works between the > different channels) then you might be able to use the channel bonding > (bond0, bond1, etc.) driver instead. If you need bridging for the mesh > interfaces, but not the LAN and/or WAN interfaces, you could mix-and-match > both types of master (virtual) interfaces.
Good hint. Looking into it, thanks! And thanks to Jerry for the confirmation that it's a real issue. Is there any interesting downside / overhead to be aware when using for example bond0 == eth1? cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel