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

On Wed, Mar 30, 2016 at 06:08:49PM +0200, Sven Eckelmann wrote:

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

Well, fastd is only a sample, though a very much used one within freifunk.

• fastd creates point2point vpn-links and makes all of them accessible via tapX

yes

• fastd only sends broadcast to its direct neighbors (vpn-links)

yes, there is a real broadcast mode, but without loop avoidance, this is basically never used.

• the fastd daemon doesn't set some flag to indicate that it doesn't really support broadcasts

yes

• 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

yes

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.

indeed Please be aware fastd is only one sample of a vpn solution, there are many others, and most of them unforseeable to us. The suggested flag would fit all of them while not disturbing the save, but traffic consuming default.

Regards, Adrian