4 ms·

FWIW; Tinc has been my workhorse between my various cloud providers, some on prem remote access for a few offices I consult with, and my home + workstations. I

FWIW; Tinc has been my workhorse between my various cloud providers, some on prem remote access for a few offices I consult with, and my home + workstations. I keep telling myself I should switch it to a wireguard mesh, but the configuration of tinc + the "right defaults" make it pretty neat. It's fun to watch as you roll out a configuration to one node in the mesh, and ping times drop suddenly once it can make a direct connection with the optimal route. I keep my provisioning script + the public keys in git; so deploying it to a new machine is a git pull, generate key, push public key, and pull on the other nodes. I have about 17+ hosts on it; not using it for very high bandwidth, but I couldn't do what I do without it.

HumanOstrich 1y ago
Tinc sounds pretty awesome, but based on the repo activity and a post from the author[1], it looks to be unmaintained. [1]: https://github.com/gsliepen/tinc/issues/443#issuecomment-1841403752 https://github.com/gsliepen/tinc/issues/443#issuecomment-184...
- jasonjayr 1y ago
  That is sadly, the biggest worry about it. Once I collect a few round tuit's, I wanted to see if I could build up a tool to build up the same mesh + routing, perhaps confined to a linux namespace so as to keep it contained, and try to reproduce the ease of configuration, on top of much better maintained core linux tools. But the key has to be -- the configuration has to be just as simple as tinc to be effective. Like, almost just parse the configuration files and build it up with WG tunnels. https://github.com/m13253/VxWireguard-Generator https://github.com/m13253/VxWireguard-Generator <-- this is what I use with a more serious "internal business" use case, so I know wireguard is in the sensitive security/encryption loop. It uses wireguard tunnels to make a broadcast/mesh Layer2 network with vxlan connections, and you then run OSPF/babel/your-favorite-routing-protocol over that.
jrm4 1y ago
Nailed it. Long time Tinc user here as well for all my personal stuff. Besides the fact that onboarding individual machines is a garbage process, it's my second best "set it and forget it thing" I use; the first being Syncthing which came later (and additionally, the two work very nicely together through weird edge cases like work VPNS and suc.)

HumanOstrich 1y ago

Tinc sounds pretty awesome, but based on the repo activity and a post from the author[1], it looks to be unmaintained. [1]: https://github.com/gsliepen/tinc/issues/443#issuecomment-1841403752 https://github.com/gsliepen/tinc/issues/443#issuecomment-184...

jasonjayr 1y ago
That is sadly, the biggest worry about it. Once I collect a few round tuit's, I wanted to see if I could build up a tool to build up the same mesh + routing, perhaps confined to a linux namespace so as to keep it contained, and try to reproduce the ease of configuration, on top of much better maintained core linux tools. But the key has to be -- the configuration has to be just as simple as tinc to be effective. Like, almost just parse the configuration files and build it up with WG tunnels. https://github.com/m13253/VxWireguard-Generator https://github.com/m13253/VxWireguard-Generator <-- this is what I use with a more serious "internal business" use case, so I know wireguard is in the sensitive security/encryption loop. It uses wireguard tunnels to make a broadcast/mesh Layer2 network with vxlan connections, and you then run OSPF/babel/your-favorite-routing-protocol over that.

jrm4 1y ago

Nailed it. Long time Tinc user here as well for all my personal stuff. Besides the fact that onboarding individual machines is a garbage process, it's my second best "set it and forget it thing" I use; the first being Syncthing which came later (and additionally, the two work very nicely together through weird edge cases like work VPNS and suc.)