4 ms·
I have used tinc [0] for this scenario successfully for 15 years. It not only supports full mesh but automatic full mesh. It will use UDP for the data stream
by rkeene2 8y ago
I have used tinc [0] for this scenario successfully for 15 years. It not only supports full mesh but automatic full mesh. It will use UDP for the data stream when possible, supports RSA and Ed25519, and supports transporting either IP or Ethernet frames.
I used the mode where it supports Ethernet frames to merge the VLANs of two datacenters across the WAN (with some additional ebtables to prevent some kinds of frames) to add the ability to migrate systems from one datacenter to another during a partial outage.
- yjftsjthsd-h 8y agoIs tinc okay security-wise? IIRC last time I looked the older crypto was really iffy looking, and the newer crypto (ED25519 rocks) was only in the dev/unstable version.
- rkeene2 8y agoThere were some issues in 1.0 that are fixed in 1.1, for which the protocol is not yet finalized although the beta releases are stable. The lack of a final release is annoying, since it does not guarantee upgrades will work with older clients but this is because the protocol isn't finalized. They are documented towards the bottom of http://tinc-vpn.org/security/ http://tinc-vpn.org/security/
- cbluth 8y agobummer its single threaded...
- mycall 8y agoI see some people experimenting and achieving more Mbit/s with their separate async thread host https://github.com/gsliepen/tinc/issues/110 https://github.com/gsliepen/tinc/issues/110