On Thu, Apr 12, 2012 at 07:12:08PM +0200, Mitar wrote:
Hi!
On Thu, Apr 12, 2012 at 5:36 PM, Andrew Lunn andrew@lunn.ch wrote:
Or, if you are in a transition phase, and don't mind your head exploding, run olsr, babel, etc, on top of BATMAN to gateway between the L2 meshes!
Can you please explain a bit more what are you thinking here?
Well, your infrastructure already speaks olsr, babel, or what every L3 mesh protocol you have. It knows how to advertise additional routes. So make one or more of your BATMAN nodes L2 mesh also a L3 mesh node. These L3 mesh nodes will see each other over the mesh, and they will see other L3 mesh nodes over what every network technology you have between L2 meshes. These L3 mesh nodes should also be the default router for the devices in the L2 mesh. The L2 mesh devices will send there packets to a L3 mesh node. It will then route it, maybe back over the mesh, or maybe over an inter mesh links, to where ever it needs to go. If ICMP redirect works on your L2 and L3 nodes, it should add host routes to the L2 nodes when they use the wrong gateway out of the L2 mesh.
Andrew