Fabian Bläse 328beebe32 fff-wireguard: Use babel type wired for wireguard babel peers ... The babel interface type 'tunnel' has some disadvantageous properties for our network. First, babel tries to evaluate the tunnel performance using the rtt. However, this makes the network quite unstable, as rtt might fluctuate a lot, especially on less reliable connections (e.g. LTE). Instead of fully falling back to an alternate route, this rtt evaluation leads to a lot of flapping routes. Additionally, rtt evaluation changes the metric of routes quite often, which leads to many unnessessary babel messages in our network. Also, babeld disables split-horizon processing on 'tunnel' interfaces per default. However, split-horizon processing can be done in our point-to-point tunnel setup without any issues and has the advantage of significantly reduced babel messages on a link with many uplink routes. Therefore, wireguard babel peers now use the interface type 'wired'. Signed-off-by: Fabian Bläse <fabian@blaese.de> Reviewed-by: Johannes Kimmel <fff@bareminimum.eu> Reviewed-by: Robert Langhammer <rlanghammer@web.de> [bump PKG_RELEASE, adjust commit title prefix] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>		2020-06-18 12:24:40 +02:00
..
files/etc	fff-wireguard: Use babel type wired for wireguard babel peers	2020-06-18 12:24:40 +02:00
Makefile	fff-wireguard: Use babel type wired for wireguard babel peers	2020-06-18 12:24:40 +02:00