On Saturday, 13 February 2021 11:07:11 CET Tushar Malpani wrote:
What is the difference between BATMAN Adv and babel routing
I keep this for another person since I don't want more conflicts with Juliusz.
But if you want to know more and have a couple of minutes than you can find
out more about babel in https://www.youtube.com/watch?v=Mflw4BuksHQ
Why use one over the other and why does babel scales over a thousand
nodes whereas BATMAN Adv has trouble doing that?
Can you please back up this claim? And batman-adv implements the routing
protocols B.A.T.M.A.N. IV and B.A.T.M.A.N. V. So you have to compare these
with babel if you want to compare routing protocols.
If you talk about the kind of traffic transported over the links then
you are talking about apples and oranges here.
Linus made an interesting Talk which discusses Layer 2 and challenges it
causes - but focuses at the end more on the multicast aspect:
And more of a general question about the design choice of BATMAN
Why go layer 2?(I read the article where present in open-mesh but
still it isn't very clear to main. What advantages do we have going
layer 2 ?)
For examples watch the beginning of the video. Maybe someone else has more
But basically, the idea for layer 2(.5) was "borrowed" from AWDS [1,2,3,4] to
achieve similar easy setups that can just use your existing infrastructure for
layer 3 management and L2 (b|m)cast by simply bridging it.
But as Linus' pointed out correctly - if you want to get this kind of
functionality then you have the problem that you got this kind of
functionality and have to deal with it.
And if you don't have this functionality you have the problem that
you don't have it and find ways to deal with it ;)