Anyone know how this compares to Tinc? I don't much know what development on it is like these days, but it for me is one of the best "set it and forget it" things I regularly use to keep my devices talking to each other.
I'm aware that with things like this you're supposed to use the latest and greatest like Wireguard or whatever, but nothing really does the p2p thing as easy as Tinc, and given secondary encryption measures (e.g. I'm sshing and httpsing to those machines) I'm just not worrying much about it right now.
Tinc will exchange endpoint information over the network, so clients will connect directly to other clients without having to set up every connection explicitly. For example, if A is configured to connect to B, and C is configured to connect to B, then A can connect to C to exchange packets directly without you having to configure that. https://tinc-vpn.org/documentation-1.1/How-connections-work....
Tinc will also do a layer 2 tunnel if you want (tap) while wireguard is only layer 3 (no broadcast/multicast).
The big con of tinc (and most VPN solutions) compared to wireguard is performance. Wireguard is a small kernel module which can process traffic very fast.
They do different things, I hear? I know Wireguard works closer to the kernel, but it's more of a traditional "VPN" otherwise, and you'd have to add "mesh."
I'm aware that with things like this you're supposed to use the latest and greatest like Wireguard or whatever, but nothing really does the p2p thing as easy as Tinc, and given secondary encryption measures (e.g. I'm sshing and httpsing to those machines) I'm just not worrying much about it right now.