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

[Feature] get remote IP #868

New Issue
Open
opened 2025-12-29 02:25:04 +01:00 by adam · 7 comments
adam commented 2025-12-29 02:25:04 +01:00
Owner
Copy Link

Originally created by @celevra on GitHub (Dec 6, 2024).

Use case

it would be great to get the real IP (not the tailscale IP) of a node

Description

the ip should be listet in the cli and in the api

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

No response

Originally created by @celevra on GitHub (Dec 6, 2024). ### Use case it would be great to get the real IP (not the tailscale IP) of a node ### Description the ip should be listet in the cli and in the api ### Contribution - [ ] I can write the design doc for this feature - [ ] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancementno-stale-bot labels 2025-12-29 02:25:04 +01:00
adam commented 2025-12-29 02:25:04 +01:00
Author
Owner
Copy Link

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

This is a bit relative, not saying we can't but we have to decide which or all.

There will be the IP that is connected to headscale, which we likely can get from the go http server.

Then there is all the discovered endpoints that the tailscale client discovers as part of magicsock. This list might include old endpoints as it is quite opportunistic.

It is a bit non obvious to which ones are useful.

What is the use case for consuming them?

@kradalby commented on GitHub (Dec 10, 2024): This is a bit relative, not saying we can't but we have to decide which or all. There will be the IP that is connected to headscale, which we likely can get from the go http server. Then there is all the discovered endpoints that the tailscale client discovers as part of magicsock. This list might include old endpoints as it is quite opportunistic. It is a bit non obvious to which ones are useful. What is the use case for consuming them?
adam commented 2025-12-29 02:25:04 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Dec 10, 2024):

for us the connected ip from go http server is what we are looking for.
it is not our main use case for tailscale but as the information exists we want to set dyndns names for devices that don't support dyndns but support tailscale

@celevra commented on GitHub (Dec 10, 2024): for us the connected ip from go http server is what we are looking for. it is not our main use case for tailscale but as the information exists we want to set dyndns names for devices that don't support dyndns but support tailscale
adam commented 2025-12-29 02:25:04 +01:00
Author
Owner
Copy Link

@codingtony-candid commented on GitHub (Feb 7, 2025):

It would be useful for audit to have access to the public ip of the nodes.

@codingtony-candid commented on GitHub (Feb 7, 2025): It would be useful for audit to have access to the public ip of the nodes.
adam commented 2025-12-29 02:25:04 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 21, 2025):

https://github.com/juanfont/headscale/issues/2152

@kradalby

@ghost commented on GitHub (Mar 21, 2025): https://github.com/juanfont/headscale/issues/2152 @kradalby
adam commented 2025-12-29 02:25:05 +01:00
Author
Owner
Copy Link

@celevra commented on GitHub (Mar 21, 2025):

so this means it gets not implemented?

@celevra commented on GitHub (Mar 21, 2025): so this means it gets not implemented?
adam commented 2025-12-29 02:25:05 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Mar 21, 2025):

No it could be, but likely not possible until I get around to reworking the connection map, which will be many releases out as there is quite a lot of other stuff in the pipeline atm.

@kradalby commented on GitHub (Mar 21, 2025): No it could be, but likely not possible until I get around to reworking the connection map, which will be many releases out as there is quite a lot of other stuff in the pipeline atm.
adam commented 2025-12-29 02:25:05 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Mar 24, 2025):

@danya0123 please post on the relevant issue, you even found it #2152.

@kradalby commented on GitHub (Mar 24, 2025): @danya0123 please post on the relevant issue, you even found it #2152.
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 enhancement no-stale-bot
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#868
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?