starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Tailscale is unable to connect to the specified port. #569

New Issue
Closed
opened 2025-12-29 02:20:37 +01:00 by adam · 2 comments
adam commented 2025-12-29 02:20:37 +01:00
Owner
Copy Link

Originally created by @MilkTeaNo7 on GitHub (Oct 17, 2023).

Problem

  1. Two servers in the same network have IP addresses in the 10.64.0.0 network segment:
    • A's IP address: 10.64.0.4
    • B's IP address: 10.64.0.8
  2. Accessing Server A, you can access port 22. I am SSHing to this server through the VPN address分配.
  3. However, I cannot communicate on other ports of Server A.
  4. It has been checked that it is not an issue with ACL.
  5. Port is in listening state as checked by ss -tlnp.
  6. Firewall is in off state.

Firewall Information

root@GW:~# iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N DOCKER
-N DOCKER-ISOLATION-STAGE-1
-N DOCKER-ISOLATION-STAGE-2
-N DOCKER-USER
-N ts-forward
-N ts-input
-A INPUT -j ts-input
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A FORWARD -o br-3d85304bf031 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o br-3d85304bf031 -j DOCKER
-A FORWARD -i br-3d85304bf031 ! -o br-3d85304bf031 -j ACCEPT
-A FORWARD -i br-3d85304bf031 -o br-3d85304bf031 -j ACCEPT
-A FORWARD -o br-5aa183c725da -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o br-5aa183c725da -j DOCKER
-A FORWARD -i br-5aa183c725da ! -o br-5aa183c725da -j ACCEPT
-A FORWARD -i br-5aa183c725da -o br-5aa183c725da -j ACCEPT
-A FORWARD -j ts-forward
-A DOCKER -d 172.19.0.2/32 ! -i br-5aa183c725da -o br-5aa183c725da -p tcp -m tcp --dport 23479 -j ACCEPT
-A DOCKER -d 172.17.0.2/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 9443 -j ACCEPT
-A DOCKER -d 172.17.0.2/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 8000 -j ACCEPT
-A DOCKER -d 172.19.0.2/32 ! -i br-5aa183c725da -o br-5aa183c725da -p udp -m udp --dport 3478 -j ACCEPT
-A DOCKER -d 172.18.0.3/32 ! -i br-3d85304bf031 -o br-3d85304bf031 -p tcp -m tcp --dport 80 -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i br-3d85304bf031 ! -o br-3d85304bf031 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i br-5aa183c725da ! -o br-5aa183c725da -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o br-3d85304bf031 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o br-5aa183c725da -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN
-A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000
-A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT
-A ts-forward -o tailscale0 -j ACCEPT
-A ts-input -s 100.64.0.4/32 -i lo -j ACCEPT
-A ts-input -s 100.115.92.0/23 ! -i tailscale0 -j RETURN
Originally created by @MilkTeaNo7 on GitHub (Oct 17, 2023). # Problem 1. Two servers in the same network have IP addresses in the 10.64.0.0 network segment: - A's IP address: 10.64.0.4 - B's IP address: 10.64.0.8 2. Accessing Server A, you can access port 22. I am SSHing to this server through the VPN address分配. 3. However, I cannot communicate on other ports of Server A. 4. It has been checked that it is not an issue with ACL. 5. Port is in listening state as checked by ss -tlnp. 6. Firewall is in off state. # Firewall Information ``` root@GW:~# iptables -S -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT -N DOCKER -N DOCKER-ISOLATION-STAGE-1 -N DOCKER-ISOLATION-STAGE-2 -N DOCKER-USER -N ts-forward -N ts-input -A INPUT -j ts-input -A FORWARD -j DOCKER-USER -A FORWARD -j DOCKER-ISOLATION-STAGE-1 -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o docker0 -j DOCKER -A FORWARD -i docker0 ! -o docker0 -j ACCEPT -A FORWARD -i docker0 -o docker0 -j ACCEPT -A FORWARD -o br-3d85304bf031 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o br-3d85304bf031 -j DOCKER -A FORWARD -i br-3d85304bf031 ! -o br-3d85304bf031 -j ACCEPT -A FORWARD -i br-3d85304bf031 -o br-3d85304bf031 -j ACCEPT -A FORWARD -o br-5aa183c725da -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o br-5aa183c725da -j DOCKER -A FORWARD -i br-5aa183c725da ! -o br-5aa183c725da -j ACCEPT -A FORWARD -i br-5aa183c725da -o br-5aa183c725da -j ACCEPT -A FORWARD -j ts-forward -A DOCKER -d 172.19.0.2/32 ! -i br-5aa183c725da -o br-5aa183c725da -p tcp -m tcp --dport 23479 -j ACCEPT -A DOCKER -d 172.17.0.2/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 9443 -j ACCEPT -A DOCKER -d 172.17.0.2/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 8000 -j ACCEPT -A DOCKER -d 172.19.0.2/32 ! -i br-5aa183c725da -o br-5aa183c725da -p udp -m udp --dport 3478 -j ACCEPT -A DOCKER -d 172.18.0.3/32 ! -i br-3d85304bf031 -o br-3d85304bf031 -p tcp -m tcp --dport 80 -j ACCEPT -A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -i br-3d85304bf031 ! -o br-3d85304bf031 -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -i br-5aa183c725da ! -o br-5aa183c725da -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -j RETURN -A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP -A DOCKER-ISOLATION-STAGE-2 -o br-3d85304bf031 -j DROP -A DOCKER-ISOLATION-STAGE-2 -o br-5aa183c725da -j DROP -A DOCKER-ISOLATION-STAGE-2 -j RETURN -A DOCKER-USER -j RETURN -A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000 -A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT -A ts-forward -o tailscale0 -j ACCEPT -A ts-input -s 100.64.0.4/32 -i lo -j ACCEPT -A ts-input -s 100.115.92.0/23 ! -i tailscale0 -j RETURN ```
adam added the bug label 2025-12-29 02:20:37 +01:00
adam closed this issue 2025-12-29 02:20:37 +01:00
adam commented 2025-12-29 02:20:38 +01:00
Author
Owner
Copy Link

@kyhwana commented on GitHub (Oct 17, 2023):

Do you have ANY ACLs set? If so, try removing them all and see what happens.

@kyhwana commented on GitHub (Oct 17, 2023): Do you have ANY ACLs set? If so, try removing them all and see what happens.
adam commented 2025-12-29 02:20:38 +01:00
Author
Owner
Copy Link

@MilkTeaNo7 commented on GitHub (Nov 12, 2023):

Do you have ANY ACLs set? If so, try removing them all and see what happens.

It's been too long, I don't know how he is now, but he seems to be fine now

@MilkTeaNo7 commented on GitHub (Nov 12, 2023): > Do you have ANY ACLs set? If so, try removing them all and see what happens. It's been too long, I don't know how he is now, but he seems to be fine now
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#569
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?