tailscale: Mullvad exit nodes need tailnet lock signing to work
What is the issue?
I have activated the Mullvad plugin but the exit nodes didn’t appear in the clients. I have the tailnet lock active and all the mullvad nodes are locked out.
The following nodes are locked out by tailnet lock and cannot connect to other nodes:
hk-hkg-wg-102.mullvad.ts.net. 100.93.104.36,fd7a:115c:a1e0:ab12:4843:cd96:625d:6824 nDYmJP3CNTRL nodekey:e64713d45bbc896bcfb965b38b732a96a0f88a62e14bf2b115f9aedcf39d6822
us-bos-wg-102.mullvad.ts.net. 100.89.129.123,fd7a:115c:a1e0:ab12:4843:cd96:6259:817b nBxKea2CNTRL nodekey:c1c9a669d24e6eec76ffad844be41b20edb506453ba76234b3a9f858d659816d
jp-tyo-wg-001.mullvad.ts.net. 100.100.131.39,fd7a:115c:a1e0:ab12:4843:cd96:6264:8327 nBuUct2CNTRL nodekey:014a36ce1434c020f2dff8e666039ee103277165aaadd304ec16d8d949648322
us-qas-wg-001.mullvad.ts.net. 100.121.87.35,fd7a:115c:a1e0:ab12:4843:cd96:6279:5723 nqoDmt5CNTRL nodekey:50a34b0a29a47b9e11a91763e9417222e04eea7bf6555a434f7bccf4ddb95722
ch-zrh-wg-005.mullvad.ts.net. 100.113.157.26,fd7a:115c:a1e0:ab12:4843:cd96:6271:9d1a nJMqgQ3CNTRL nodekey:755fda1e1c06d1f9a9d17baf4afadd5a30ad77284f0c316213f9eebffd719d13
au-syd-wg-002.mullvad.ts.net. 100.67.91.114,fd7a:115c:a1e0:ab12:4843:cd96:6243:5b72 n9jS4K4CNTRL nodekey:95478300ecbe8808590eecf9fbace1d02a3cc1972cdda85dbb68dfa90a035b71
us-atl-wg-203.mullvad.ts.net. 100.74.210.123,fd7a:115c:a1e0:ab12:4843:cd96:624a:d27b ncfSyp4CNTRL nodekey:9d942f23ed99cc30b6b62b6892359ca236e3be7e1bc47ae153383550afcad277
gb-mnc-wg-001.mullvad.ts.net. 100.104.54.116,fd7a:115c:a1e0:ab12:4843:cd96:6268:3674 nXfGuh5CNTRL nodekey:43692124b6d3485c66a693c61e0ab61ddc4c431ec27333d90a05696193283673
se-sto-wg-002.mullvad.ts.net. 100.122.174.102,fd7a:115c:a1e0:ab12:4843:cd96:627a:ae66 nFAa8J1CNTRL nodekey:ab66593dfba63da4559780c97f335d405fc61df7ba0580334361996476faae62
us-lax-wg-102.mullvad.ts.net. 100.108.108.45,fd7a:115c:a1e0:ab12:4843:cd96:626c:6c2d nE3zFD4CNTRL nodekey:2ddc2f6ecea63b111ba572d103767faa6132268db0553750f78fafdd416c6c1c
...
After I’ve signed one exit node it appeared in the list and I could use it.
Steps to reproduce
Activate mullvad plugin with tailscale lock enabled.
Are there any recent changes that introduced the issue?
No response
OS
Linux, macOS, Windows, iOS, Android, Synology, Other
OS version
Ventura 13.5.2, iOS 17
Tailscale version
1.48.2
Other software
No response
Bug report
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 24 (3 by maintainers)
There is a difference between purely exit nodes and non-exit nodes though. I understand this probably makes sense as an default here, but I think that nodes that are purely exit nodes (e.g, cant initiate a connection to your tailnet) should have an option to be excluded from this.
If I’m signing these mullvad nodes, what exactly am I attesting, and gaining from attesting them? What’s the security posture? These nodes are already outside of my control. There is nothing stopping mullvad from, for example, sharing the cryptographic material of a node with a third party. I wouldn’t notice that as I’ve already attested that cryptographic material.
A more general solution here would be that I sign a setting on my tailnet saying that purely exit nodes (can probably be inferred client side based on ACLs) do not need to be signed.
Here is a zsh script to sign the nodes in bulk:
Just came across this issue while searching why the mullvad nodes were not showing in my tailscale client. Maybe having a quick note or popup on the client to “warn” about this would be enough? Just to give a bit more visibility.
I do agree that if you’d op in for network lock, you’d want to keep the mechanism in place to “manually” authorize new nodes
I’m surprised this is closed. Just because you can go sign the nodes, doesn’t make this user friendly.
A small footnote that says you need to sign nodes isn’t helpful when you pay for something and nothing appears in your exit node list.
Providing a lock sign command for a region of mullvad nodes would help.
Even better would be a providing a list of the node names, it’s hard to find the ones you want to sign in that mega list because there is no page with a mapping of location -> .ts.net node values either.
Hello, I am struggling with same problem, but now signing mullvad nodes doesn’t even work from my terminal it says:
error: 500 Internal Server Error: signing failed: request returned (404): node not foundeven if I can clearly see and copy signing nodekey from the list that was returned bytailscale lock status --jsonI paid for that addon but to be honest if this is the state of that feature I will resign. Just an official website with all mullvad exit-nodes with ready to copy command could be enough even for beta.
I was thinking for a way to sign all the mullvad exit nodes at once. Also there is the issue when the mullvad servers are offline and new ones are available. You have to keep signing the exit nodes before using.
This is what I ended up doing.
Thank you!
So do I need to sign all the mullvad nodes I want to use? There are several hundred.
Thank you!
I don’t understand the feature request: the mullvad nodes need to be signed with the key that only the tailnet owner possesses. Is the request to make this more clear somewhere?