Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] get remote IP #2272

Open
2 tasks
celevra opened this issue Dec 6, 2024 · 2 comments
Open
2 tasks

[Feature] get remote IP #2272

celevra opened this issue Dec 6, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@celevra
Copy link

celevra commented 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

@celevra celevra added the enhancement New feature or request label Dec 6, 2024
@kradalby
Copy link
Collaborator

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?

@celevra
Copy link
Author

celevra commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants