Re: [B.A.T.M.A.N.] Migration to Batman

Gioacchino Mazzurco
2012-04-12T10:36:27Z

Hao! Ma allora sei stronzo !!

>As I
> understand, we should be migrating the whole network at same time each
> time a new version of Batman (or Linux kernel) is released, because
> you do not keep things backwards compatible? How serious is this
> limitation in practice?

It happen just some times not every batman/kernel version change.
We use batman-adv in Ninux Pisa and in Ninux Sicily and we managed have
some compatibility break in updates without problem just start to update
from the fairest node to the yours

> I am also a bit afraid of L2 meshing. How problematic are floods in
> the network in practice? Like people broadcasting stuff and so on? Are
> there any filters possible for this?

II have tried to do something about filtering but without success, but
we never encountered flooding problems nor in Pisa nor in Sicily

> We have a setup where nodes have WiFi connections and VPN links to
> central server. We are thinking of migration OpenVPN to L2TP tunnels,
> so on the central server there will be many tunnels dynamically
> created as nodes connect and disconnect. Is Batman able to add
> interfaces it operates during run-time? Probably we should not just
> bridge all tunnels and run Batman on top of that? This would probably
> hide that there are different links bellow from Batman? Or not? (For
> example, on OLSR we should not do this, because then nodes would
> discover each other over server as one hop/direct neighbors.)

In batman-adv you can add/remove interfaces at runtime without problems
so you doesn't need bridging or similar nasty things

On 04/12/12 12:26, Mitar wrote:
> Hi!
>
> I really liked your client roaming support presented at Battlemesh.
> But I am still afraid to deploy Batman in the network. As I
> understand, we should be migrating the whole network at same time each
> time a new version of Batman (or Linux kernel) is released, because
> you do not keep things backwards compatible? How serious is this
> limitation in practice?
>
> I am also a bit afraid of L2 meshing. How problematic are floods in
> the network in practice? Like people broadcasting stuff and so on? Are
> there any filters possible for this?
>
> We have a setup where nodes have WiFi connections and VPN links to
> central server. We are thinking of migration OpenVPN to L2TP tunnels,
> so on the central server there will be many tunnels dynamically
> created as nodes connect and disconnect. Is Batman able to add
> interfaces it operates during run-time? Probably we should not just
> bridge all tunnels and run Batman on top of that? This would probably
> hide that there are different links bellow from Batman? Or not? (For
> example, on OLSR we should not do this, because then nodes would
> discover each other over server as one hop/direct neighbors.)
>
>
> Mitar