Re: [B.A.T.M.A.N.] No rebroadcast on mesh links

Sven Eckelmann
2016-03-30T16:08:49Z

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

On Wednesday 30 March 2016 15:58:42 Adrian Reyer wrote:
> A current setup of a freifunk gateway in my freifunk-community hast 2
> interfaces attached to a batman instance, 1 fastd reaching all the
> nodes, here we absolutely need rebroadcasts and 1 tinc interface
> connecting alle the gateways, there we have full mesh due to tinc
> already and don't need rebroadcasts. Both interfaces are just
> tap-Devices, e.g. tap0 and tap1.

I never used fastd. So maybe you can tell me if I summarize it correctly:

* fastd creates point2point vpn-links and makes all of them accessible via
tapX
* fastd only sends broadcast to its direct neighbors (vpn-links)
* the fastd daemon doesn't set some flag to indicate that it doesn't really
support broadcasts
* you want batman-adv to behave on this tapX exactly like on adhoc (maybe
with less re-broadcasts than on adhoc) to keep everything in the same
broadcast domain

And for tinc you most likely have configured mst for broadcasts ("tinc
handles the forwarding via spanning tree") and don't need batman-adv
anymore for re-broadcasts.

Kind regards,
Sven

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