no public network Endpoints #687

Closed
opened 2025-12-29 02:22:03 +01:00 by adam · 8 comments
Owner

Originally created by @cheng990629 on GitHub (Apr 7, 2024).

Bug description

no public network Endpoints
I have configured port forwarding for a Tailscale client with the IP address 10.20.1.20 on my server with the public IP address 223.22.22.1. However, when attempting to ping the Tailscale client from within the same subnet (10.20.1.0/24), the traffic is routed through the Tailscale relay server instead of using the port forwarding configuration.

Environment

  • OS: Ubuntu Ubuntu 23.10
  • Headscale version: v0.23.0-alpha5
  • Tailscale version: 1.60.1

To Reproduce

  1. Set up port forwarding for Tailscale client 10.20.1.20 on server with public IP 223.22.22.1.
  2. From another device within the same subnet (10.20.1.0/24), ping Tailscale client 10.20.1.20.

Logs and attachments

I have attached the following files:

  • ACL configuration
  • Headscale configuration

Additionally, here is the netmap dump of the Tailscale client:

tailscale debug netmap > tailscale_netmap.json

Please let me know if any further information is needed.

Originally created by @cheng990629 on GitHub (Apr 7, 2024). ## Bug description no public network Endpoints I have configured port forwarding for a Tailscale client with the IP address 10.20.1.20 on my server with the public IP address 223.22.22.1. However, when attempting to ping the Tailscale client from within the same subnet (10.20.1.0/24), the traffic is routed through the Tailscale relay server instead of using the port forwarding configuration. ## Environment - OS: Ubuntu Ubuntu 23.10 - Headscale version: v0.23.0-alpha5 - Tailscale version: 1.60.1 ## To Reproduce 1. Set up port forwarding for Tailscale client 10.20.1.20 on server with public IP 223.22.22.1. 2. From another device within the same subnet (10.20.1.0/24), ping Tailscale client 10.20.1.20. ## Logs and attachments I have attached the following files: - ACL configuration - Headscale configuration Additionally, here is the netmap dump of the Tailscale client: `tailscale debug netmap > tailscale_netmap.json` Please let me know if any further information is needed.
adam added the stalebug labels 2025-12-29 02:22:03 +01:00
adam closed this issue 2025-12-29 02:22:03 +01:00
Author
Owner

@cheng990629 commented on GitHub (Apr 7, 2024):

tailscale_netmap.json

@cheng990629 commented on GitHub (Apr 7, 2024): [tailscale_netmap.json](https://github.com/juanfont/headscale/files/14896074/tailscale_netmap.json)
Author
Owner

@cheng990629 commented on GitHub (Apr 7, 2024):

./Tailscale ping 100.64.0.10
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 24ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 45ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 46ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 57ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 37ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 47ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 43ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 48ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 48ms
pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 46ms
2024/04/07 15:12:42 direct connection not established

@cheng990629 commented on GitHub (Apr 7, 2024): ./Tailscale ping 100.64.0.10 pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 24ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 45ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 46ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 57ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 37ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 47ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 43ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 48ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 48ms pong from csd-vpn-router-client (100.64.0.10) via DERP(kr) in 46ms 2024/04/07 15:12:42 direct connection not established
Author
Owner

@ohdearaugustin commented on GitHub (May 18, 2024):

This is issue is really hard to reproduce, as port-forwarding could be achieved in several different ways.

The only hint I can think out is that, somehow the connection couldn't be established directly toward the server. Therefore, it was falling back to DERP. This is probably a setup issue and not a bug in headscale.

@ohdearaugustin commented on GitHub (May 18, 2024): This is issue is really hard to reproduce, as port-forwarding could be achieved in several different ways. The only hint I can think out is that, somehow the connection couldn't be established directly toward the server. Therefore, it was falling back to DERP. This is probably a setup issue and not a bug in headscale.
Author
Owner

@colaH16 commented on GitHub (Jun 11, 2024):

I Have Same Issue.

I have 2 machines on Oracle Cloud Infrastructure.

one machine is connected to tailscale.
The other one is connected to headscale.

tailscale netmap said something wrong.
The endpoints of the machines connected to tailscale are as follows

			"Endpoints": [
				"168.138.32.189:41641",
				"[2603:c023:8:d312::d03]:41641",
				"10.123.12.3:41641",
				"172.17.0.1:41641",
				"172.23.255.1:41641",
				"172.24.0.1:41641"
			],

On the other hand, the endpoints on the machine connected to headscale look like this

		"Endpoints": [
			"10.123.12.12:41641"
		],

How to set Endpoints as public?

@colaH16 commented on GitHub (Jun 11, 2024): I Have Same Issue. I have 2 machines on Oracle Cloud Infrastructure. one machine is connected to tailscale. The other one is connected to headscale. tailscale netmap said something wrong. The endpoints of the machines connected to tailscale are as follows ``` "Endpoints": [ "168.138.32.189:41641", "[2603:c023:8:d312::d03]:41641", "10.123.12.3:41641", "172.17.0.1:41641", "172.23.255.1:41641", "172.24.0.1:41641" ], ``` On the other hand, the endpoints on the machine connected to headscale look like this ``` "Endpoints": [ "10.123.12.12:41641" ], ``` How to set Endpoints as public?
Author
Owner

@github-actions[bot] commented on GitHub (Sep 10, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Sep 10, 2024): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@kradalby commented on GitHub (Sep 10, 2024):

Please try the latest beta.

@kradalby commented on GitHub (Sep 10, 2024): Please try the latest beta.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 26, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Dec 26, 2024): This issue is stale because it has been open for 90 days with no activity.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 2, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jan 2, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#687