Bug #14676
open
Listening Port option in the Tailscale configurator is not respected
0%
Description
The tailscaled process starts and listens on a random port, instead of the one specified. This causes things like direct tunnels between tailscale node to not work (WAN rule), thus causing all traffic to be relayed when the other device is behind double NAT or other hard NAT types. If I go and see what port is actually being used and adjust me WAN rule, suddenly direct connections are all established.
How to reproduce:
1. Set a listening port
2. Start the tailscale service
3. View what the actual port is being listened on by executing "sockstat -l"
Files
Updated by aleksei prokofiev over 1 year ago
- File clipboard-202308101325-uwqzq.png clipboard-202308101325-uwqzq.png added
- File clipboard-202308101326-phhsa.png clipboard-202308101326-phhsa.png added
- File clipboard-202308101330-w5p58.png clipboard-202308101330-w5p58.png added
- File clipboard-202308101331-85elw.png clipboard-202308101331-85elw.png added
- File clipboard-202308101331-bq7cl.png clipboard-202308101331-bq7cl.png added
Tested on 2.7.0 and 23.05.1 , Tailscale 0.1.4
Can not reproduce, if I change listen port it always changed appropriate the settings
Updated by Christian McDonald over 1 year ago
I'm not able to replicate this report myself.
Updated by David G over 1 year ago
- File Screenshot 2023-08-10 094756.png Screenshot 2023-08-10 094756.png added
- File Screenshot 2023-08-10 094710.png Screenshot 2023-08-10 094710.png added
Christian McDonald wrote in #note-2:
I'm not able to replicate this report myself.
Here are some screenshots of the issue happening on my end. I will try to reinstall the package and see what happens.
Updated by David G over 1 year ago
David G wrote in #note-3:
Christian McDonald wrote in #note-2:
I'm not able to replicate this report myself.
Here are some screenshots of the issue happening on my end. I will try to reinstall the package and see what happens.
After reinstalling the package, the service started back up, however, now it's listening on different random ports.
Updated by Christian McDonald over 1 year ago
I bet something else is already listening on 11111, forcing tailscaled to choose another port to bind.
Updated by Christian McDonald over 1 year ago
- Status changed from New to Not a Bug
Updated by David G over 1 year ago
Christian McDonald wrote in #note-5:
I bet something else is already listening on 11111, forcing tailscaled to choose another port to bind.
I just tried another port, but also confirmed nothing is listening on it before setting it. I also completely killed the tailscaled process and started it back up. The next thing I tried was a log out and clean, but that also did not do anything. The port is still random. Anything else I can try?
Updated by David G over 1 year ago
David G wrote in #note-7:
Christian McDonald wrote in #note-5:
I bet something else is already listening on 11111, forcing tailscaled to choose another port to bind.
I just tried another port, but also confirmed nothing is listening on it before setting it. I also completely killed the tailscaled process and started it back up. The next thing I tried was a log out and clean, but that also did not do anything. The port is still random. Anything else I can try?
Alright, I found the issue. If I don't use a custom control server and use tailscales, the issue does not occur and the port setting is respected. As soon as I specify my own control server, the port is randomized. Please confirm if this is reproducible on your end.
Updated by Christian McDonald over 1 year ago
- Status changed from Not a Bug to Confirmed
Updated by aleksei prokofiev 10 months ago
The same behaviour on
23.09.1-RELEASE (amd64)
built on Tue Jan 30 15:33:00 MST 2024
FreeBSD 14.0-CURRENT
If use custom server te listen ports are randomized