Repository navigation
FR: Choose remote port with Mullvad VPN exit nodes #9452
Description
What are you trying to do?
Some networks block UDP traffic in specific ports in an effort to firewall VPN access. Mullvad exit nodes in Tailscale use port 51820, which is blocked in a few networks I use on my laptop.
The dedicated Mullvad VPN app supports setting the connection port to 53, which is the same as DNS, which gets around such firewalls, as they can't block port 53 without breaking DNS.
How should we solve this?
Add the ability to set the remote port on Mullvad exit nodes, either in-app or through the Admin console.
What is the impact of not solving this?
Mullvad exit nodes are completely unusable in networks with restrictive firewalls without a mechanism like this.
Anything else?
Mullvad mentions this capability in their app in passing in their FAQ when talking about a Comcast gateway: https://mullvad.net/en/help/faq/#71
Activity
tabithamoon commentedon Sep 20, 2023
If possible, an alternative would be to automatically try reaching out through port 53 if it notices it can't connect to Mullvad through the normal 51820 port, which would be better from a user experience stand point.
JonnieCache commentedon Jun 17, 2024
I am in this exact position, my local library blocks port 51820. Using the mullvad client I can send the wireguard traffic through port 53 (or 443 etc.) With the tailscale integration it simply cannot be made to work :/
The library also blocks port 22, so being able to tunnel out is vital to me actually getting any work done unfortunately, and exiting through my home LAN isn't really a good solution.