[Battlemesh] TincVPN with routing protocols for WBMv13?
vincent.wiemann at ironai.com
Fri Oct 16 00:43:39 CEST 2020
tinc's performance is bad on devices with little resources. That's why we
use fastd. We have experimentally implemented io_uring support. With that fastd is
the fastest userspace VPN and we run it seamlessly with Babel as it supports
TAP (you lose some MTU bytes because of the ethernet header).
There is a pull-request on Github in freifunk-gluon for a WireGuard broker.
WireGuard is the preferred way in my eyes because of its unmatchable performance,
but the broker needs some security measures to be implemented for large-scale deployment.
I'd love to see you find a solution we can all profit from.
On 15.10.20 19:22, Mitar wrote:
> Have you tried Tunneldigger?
>> In the past I ran Tinc+babel over my server as an entry point, Tinc
>> has some weird internal ways to do the routing, but it has also a mode
>> to delegate the routing to a proper routing daemon, like Babel or any
>> other one.
>> Anyone interested to play with Tinc+Babel (or any other) during WBMv13?
>> I guess we could also try Wireguard or OpenVPN in TAP over UDP mode...
>> Let me know what you think.
>> Benjamin Henrion (zoobab)
>> Email: zoobab at gmail.com
>> Mobile: +32-484-566109
>> Web: http://www.zoobab.com
>> FFII.org Brussels
>> "In July 2005, after several failed attempts to legalise software
>> patents in Europe, the patent establishment changed its strategy.
>> Instead of explicitly seeking to sanction the patentability of
>> software, they are now seeking to create a central European patent
>> court, which would establish and enforce patentability rules in their
>> favor, without any possibility of correction by competing courts or
>> democratically elected legislators."
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
More information about the Battlemesh