Re: [B.A.T.M.A.N.] Batman-adv and routed subnets

[Sven Eckelmann <sven@narfation.org>]

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

On Friday 03 August 2012 11:40:43 Luca Pretto wrote:
> Thanks for your answer Sven.
> 
> So, I've obviously misunderstood the part "mixing non-B.A.T.M.A.N. systems
> with batman-adv" [&]

This thing only explains how to connect non-batman-adv systems like you would 
to with a switch... not routing.

> I admit: the fact that batman-adv operates al L2
> really confuses me a lot! I'm a DIY nerd with no background training, so
> it's quite difficult to me.. But I won't give up! ;D

Just imagine that the mesh is a big switch. Such a thing that you have 
(propably) on your table. This version is not in one box, but build using 
connected small boxes. It depends on you how you want to give clients access 
to this switched network... just use L2 switches/bridges to connect them or 
use L3 routing to create smaller broadcast domains.

> So, do you think that I should try to setup OSPF on every node, to keep the
> thing as-much-auto-scaling-as-possible?

Sry, will leave that open for someone else.

> But in that case I suspect I won't be able to use the "Gateway support"
> functions. Is it correct? [%]

The gateway support stuff is just for DHCP routing. It helps sent a DHCP 
packet to the best gateway. And your setup (that routes packets) will not sent 
DHCP packets from clients over the mesh, but instead each router has to answer 
it. So yes, normal L3 setups will not benefit from the gateway support. You 
may still use it when you configure the dhcp server on the routers as dhcp-
relay-agent (but only when they still forward the request as broadcast and not 
as unicast to a preconfigured server).

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]