charizardcharz

I have Tailscale directly installed on the host and I don't use Mullvad so I haven't tried that setup myself.

Looks like you would need to set the TS_EXTRA_ARGS environment variable in your container to --exit-node= --exit-node-allow-lan-access=true with the exit node name or ip of the Mullvad node. I haven't tried this myself though.

That's great to hear! Gluetun looks interesting, I'll check it out and maybe migrate if it works for me.

I haven't used that feature so I can't really say, but I don't see how it would affect it. You're not modifying anything on the tailscale side and you're not adding nodes to your tailnet, you only have the same one for the host system.

Tailscale was updated with direct support for Mullvad, but since you already have Proton I'm guessing you wouldn't want to switch.

If you're using containers, you can have one container with your VPN and route traffic from specific containers through the VPN container. You can then have tailscale on the host system.

There's a quick guide on setting up the VPN part here. Tailscaile you set up normally.

You can use one of your nodes as an exit node for another device and route your traffic though it as an alternative to a public VPN, depending on your needs.

I use it for remote management, video streaming, and the occasional file transfer without publicly exposing my NAS. You could achive all this by setting up your own wireguard server but that's more work.

I'm surprised you're finding it too slow for video streaming. I use it just fine and can saturate my 300 Mbit connection when doing file transfers.

It is, along with a bunch of alternative frontends. The old.lemmy one is mlmym with the dev’s deployment at mlmym.org or you can self-host it using the docker image.