You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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
How can it be implemented?
No response
The text was updated successfully, but these errors were encountered: