Remix.run Logo
▲ 8fingerlouie 2 hours ago

Compared to faffing around with certificates, Wireguard or if you're lazy, Tailscale, is a breeze to setup.

Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance.

Tailscale is easier (presumably), but also puts a corporate entity between you and your data.

▲devilbunny an hour ago | parent [-]

Tailscale is ridiculously easy, and headscale is a thing. It doesn't support everything corporate Tailscale does, but it covers the basics of "get me into my network from anywhere". You can run it on a $1/month VPS that has a public IPv4 address.

I don't work with computers professionally, at all. It still only took me about 2 hours to get the VPS, get Debian going on it, set up headscale, and connect to it from home. Do I still use corporate Tailscale? Yes, it has some features that aren't beautifully supported on headscale, and so for the moment I'm fine with that. But I do have my backup plan in place if I need it.

▲rlt 32 minutes ago | parent [-]

Personally I’d rather let Tailscale manage securing the public-facing service than use Headscale. Tailnet Lock seems like a good compromise. And as much as I’d like to use it, I don’t trust Tailscale SSH.

▲devilbunny 14 minutes ago | parent [-]

I agree, but if people want no corporate dependency at all, it's there.

I have a headscale instance, on one of those $1/mo VPSes, and I don't intend to use it unless I have to. But if I have to, it's there.