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

How do I know if clients are really connected directly #329

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

Originally created by @Zhuangkh on GitHub (Sep 18, 2022).

Issue description

I have deployed one headscale server and four tailscale clients. When I use the tailscale status command, I find that some clients show the IP of the Headscale server even though they display direct. Does this mean that the two clients are not really direct connected to each other, but are using the headscale server as a relay?

Thanks for this wonderful project.

Context info

  • Version of headscale used: v0.16.4
  • Version of tailscale client:
    • windows 1.30.2
    • debian 1.30.2

image

image

Originally created by @Zhuangkh on GitHub (Sep 18, 2022). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the issue in this language. --> <!-- If you have a question, please consider using our Discord for asking questions --> **Issue description** <!-- Please add your issue description. --> I have deployed one headscale server and four tailscale clients. When I use the `tailscale status` command, I find that some clients show the IP of the Headscale server even though they display `direct`. Does this mean that the two clients are not really direct connected to each other, but are using the headscale server as a relay? Thanks for this wonderful project. **Context info** <!-- Please add relevant information about your system. For example: - Version of headscale used - Version of tailscale client - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version - Kernel version - The relevant config parameters you used - Log output --> - Version of headscale used: `v0.16.4` - Version of tailscale client: - windows `1.30.2` - debian `1.30.2` ![image](https://user-images.githubusercontent.com/30818313/190893530-53b5c763-f4f7-4f61-a3e0-a51095678a72.png) ![image](https://user-images.githubusercontent.com/30818313/190893639-d4c5ea07-9562-4e72-8f1d-b1f24a66877d.png)
adam added the bug label 2025-12-29 01:27:05 +01:00
adam closed this issue 2025-12-29 01:27:06 +01:00
adam commented 2025-12-29 01:27:06 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Sep 20, 2022):

Can you please raise this in Discord? Thanks!

@juanfont commented on GitHub (Sep 20, 2022): Can you please raise this in Discord? Thanks!
adam commented 2025-12-29 01:27:07 +01:00
Author
Owner
Copy Link

@Zhuangkh commented on GitHub (Sep 21, 2022):

I finally found out that this Issue came from my mistake. My gateway uses a proxy to send the DREP request, so the final display is the IP of the direct connection to the proxy server.

FYI, I fixed it by adding the proxy rule.

@Zhuangkh commented on GitHub (Sep 21, 2022): I finally found out that this Issue came from my mistake. My gateway uses a proxy to send the DREP request, so the final display is the IP of the direct connection to the proxy server. FYI, I fixed it by adding the proxy rule.
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#329
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?