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] Is it possible to prevent different users from seeing each other's nodes? #944

New Issue
Closed
opened 2025-12-29 02:26:32 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:26:32 +01:00
Owner
Copy Link

Originally created by @agostop on GitHub (Feb 16, 2025).

Use case

Prevent clients from querying nodes that do not belong to their own namespace unless ACL allows it

Description

For example, there are two tenants, user1 and user2. When user1 uses tailscale status locally, he can only see the nodes in his own namespace.
But, If acl rule allow user1 to access some node of user2, then user1 can see those nodes when using 'tailscale status'.

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 @agostop on GitHub (Feb 16, 2025). ### Use case Prevent clients from querying nodes that do not belong to their own namespace unless ACL allows it ### Description For example, there are two tenants, user1 and user2. When user1 uses tailscale status locally, he can only see the nodes in his own namespace. But, If acl rule allow user1 to access some node of user2, then user1 can see those nodes when using 'tailscale status'. ### 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 enhancementfaq labels 2025-12-29 02:26:32 +01:00
adam closed this issue 2025-12-29 02:26:32 +01:00
adam commented 2025-12-29 02:26:32 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Feb 16, 2025):

No, this is not possible and documented in the tailscale docs.

If traffic is allowed to flow one way, then both needs to be in each others netmap.

This has been discussed multiple times before, please ask in discord or search the GitHub tracker.

@kradalby commented on GitHub (Feb 16, 2025): No, this is not possible and documented in the tailscale docs. If traffic is allowed to flow one way, then both needs to be in each others netmap. This has been discussed multiple times before, please ask in discord or search the GitHub tracker.
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 faq
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#944
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?