Tailscale vs. Narrowlink
11–20 of 162 posts
Re: Tailscale vs. Narrowlink
#12> However, tailscale focuses on access different devices to each other, while Narrowlink focuses on access to the services trough on the agent as a proxy. You can easily do the same thing with Tailscale: https://tailscale.com/kb/1019/subnets/ .
Re: Tailscale vs. Narrowlink
#13Thanks for the pointer to headscale - will take a look ;)
Re: Tailscale vs. Narrowlink
#14This article is classic SEO fluff right? The Q&A style answering exactly the type of questions that people comparing the two would write into google search.
Re: Tailscale vs. Narrowlink
#15Don't forget Nebula[1]. [1] https://slack.engineering/introducing-nebula-the-open-source...
Re: Tailscale vs. Narrowlink
#16>Narrowlink uses a centralized gateway that clients and agents connect to over HTTP/S protocols
Tunneling TCP over TCP will undoubtedly result in poor network performance. This is why WireGuard is UDP-only.
Re: Tailscale vs. Narrowlink
#17Re: Tailscale vs. Narrowlink
#18For people for which the SaaSiness of Tailscale would be the main deciding factor, it is important to note that this article completely fails to mention Headscale, a BSD-licenced tailscale-compatible coordination server under active development
Re: Tailscale vs. Narrowlink
#19I think they are comparing apple to orange here.
Re: Tailscale vs. Narrowlink
#20For people for which the SaaSiness of Tailscale would be the main deciding factor, it is important to note that this article completely fails to mention Headscale, a BSD-licenced tailscale-compatible coordination server under active development
We tried switching to Headscale recently...it was not a pleasant experience. I'm sure with more time in the oven, it will eventually become a comparable replacement, but I wouldn't be relying on it for anything production oriented.
The interface is a bit clunky but the service (both agent and control plane) are rock solid for me.