runtime, tailscale, elixir, python: support peer lookup by ip#145
Merged
Conversation
npry
force-pushed
the
npry/ip_lookup
branch
8 times, most recently
from
c6fb902 to
491aae3
Compare
danderson
approved these changes
Apr 30, 2026
Member
danderson
left a comment
danderson
left a comment
There was a problem hiding this comment.
lgtm, modulo the inefficient route lookups that could be barted. The APIs look right though, so if you want to defer dealing with that, I'm find with a filed issue so we don't forget.
npry
force-pushed
the
npry/ip_lookup
branch
2 times, most recently
from
69a1662 to
749e86d
Compare
Signed-off-by: Nathan Perry <nathan@tailscale.com> Change-Id: I2ee105905ac575b4f83c0dbae7e35d466a6a6964
Signed-off-by: Nathan Perry <nathan@tailscale.com> Change-Id: I5a6e7e7e9b1cd186bbfdb39f6c2b54cc6a6a6964
Signed-off-by: Nathan Perry <nathan@tailscale.com> Change-Id: I5f411617ddbfe22b2390ad08355021256a6a6964
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two separate functions are supported: lookup by tailnet IP (unambiguous) and lookup by accepted routes. The accepted routes lookup may in principle return more than one answer, e.g. if there are two subnet routers active on the same subnet.
The short-term motivation here is to support identity integrations, e.g. answering "what peer is responsible for this request?" in the axum example, as a piece of the puzzle for application capability rules