Comment

charizardcharz@lemmy.world ⁨1⁩ ⁨year⁩ ago

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.

source

Sort:hotnew top

LunchEnjoyer@lemmy.world ⁨1⁩ ⁨year⁩ ago
I ended up doing this and it worked swimmingly! ✨

Big shout out to Glueton VPN for making it so easy!

https://github.com/qdm12/gluetun

source
- charizardcharz@lemmy.world ⁨1⁩ ⁨year⁩ ago
  That’s great to hear! Gluetun looks interesting, I’ll check it out and maybe migrate if it works for me.
  
  source
ShinyBook@lemmy.world ⁨1⁩ ⁨year⁩ ago
Have you figured out how to use the Mullvad VPN from Tailscale for a similar setup like you’ve linked? I cannot figure out how to get a tailscale docker container to properly connect to an exit node.

source
- keyez@lemmy.world ⁨1⁩ ⁨year⁩ ago
  I use a binhex-privoxyvpn container with a mullvad wireguard config in there. That’s for my server and containers at least.
  
  source
- charizardcharz@lemmy.world ⁨1⁩ ⁨year⁩ ago
  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.
  
  source
notfromhere@lemmy.one ⁨1⁩ ⁨year⁩ ago
Do you know how it works with tailscale lock?

source
- charizardcharz@lemmy.world ⁨1⁩ ⁨year⁩ ago
  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.
  
  source
  - notfromhere@lemmy.one ⁨1⁩ ⁨year⁩ ago
    I subscribed to the mullvad addon to try it out and saw about 30+ mullvad nodes waiting to be signed, probably signed due to the lock. That got me thinking I probably want to configure the NACL so the mullvad nodes I allow on my tailnet are not able to initiate any connections to my other nodes. I didn’t see any documentation on my setup so cancelled the mullvad addon until I have time to dig into it more.
    
    source