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

Adrian Reyer
2016-03-30T19:55:05Z

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

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
--
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91
Mail: lihas@lihas.de - Web: http://lihas.de
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 465 bytes --]