golink VS innernet

Something else interesting they're doing is their tsnet package, which lets you join your process to the tailnet and bind tcp listeners/connect to TCP services via their tailnet IP or subnet.

I'm writing some stuff using this at the moment, but I also just saw https://github.com/tailscale/golink which does the same thing: a single binary that runs a link shortener that joins itself to your tailnet.

tl;dr: don't run your service on a machine then join that to tailnet, directly bind your service to an in-memory tailnet client

Innernet is a barebone alternative. https://github.com/tonarino/innernet

Very relatable! At first, I struggled for days trying to make Netmaker or Innernet functional for my personal home server (Raspberry Pi behind multiple routers). But then I stumbled upon ZeroTier, and everything worked seamlessly within a couple of hours. Tailscale was actually the next one on my list because I heard many positive things about it over at r/selfhosted (especially about headscale). However, I did not end up testing it after ZeroTier worked.

Not if you are running wireguard without any management client/server like Netmaker or innernet or any of the many others like them.

I use the GCP free instance as my innernet coordination server (Wireguard mesh vpn). Which is extremely low traffic.

Or why not the open source tool innernet? https://github.com/tonarino/innernet

I wonder if this might improve over a more modern transport, if you were using an IPSec VPN.

Wireguard is enabling us to re-think what's possible over a VPN. Here's an example of what I mean. The network stack is based on Wireguard, with https://github.com/tonarino/innernet providing the topology and identity provisioning.

Virtual Private Network: Innernet, MASQ