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

Nodes shared in namespace #66

New Issue
Closed
opened 2025-12-29 01:21:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 01:21:31 +01:00
Owner
Copy Link

Originally created by @12nick12 on GitHub (Oct 23, 2021).

NodeA_NameSpaceA, NodeB_NamespaceB -> both shared to NameSpaceC.

Shouldn't the two of them be able to talk? This includes routed subnets.

This doesn't appear to work that way. I would have to either have to share NodeA in NameSpaceB or vise versa.

Otherwise this is pretty awesome, thanks.

Originally created by @12nick12 on GitHub (Oct 23, 2021). NodeA_NameSpaceA, NodeB_NamespaceB -> both shared to NameSpaceC. Shouldn't the two of them be able to talk? This includes routed subnets. This doesn't appear to work that way. I would have to either have to share NodeA in NameSpaceB or vise versa. Otherwise this is pretty awesome, thanks.
adam closed this issue 2025-12-29 01:21:31 +01:00
adam commented 2025-12-29 01:21:32 +01:00
Author
Owner
Copy Link

@a1ad commented on GitHub (Oct 28, 2021):

Can confirm:

Headscale:
image

Owncloud server > no FW node found.
image

@a1ad commented on GitHub (Oct 28, 2021): Can confirm: Headscale: ![image](https://user-images.githubusercontent.com/29516835/139203416-8630808e-4b85-4022-ba25-3e30cefd7121.png) Owncloud server > no FW node found. ![image](https://user-images.githubusercontent.com/29516835/139200778-eeec2d6d-7a1b-4fb4-8cdb-d96094fa26a9.png)
adam commented 2025-12-29 01:21:32 +01:00
Author
Owner
Copy Link

@juanfont commented on GitHub (Oct 30, 2021):

Shared nodes do not expose their subnets, to match the behaviour Tailscale.com has (https://tailscale.com/kb/1084/sharing/#sharing--subnets-subnet-routers)

And shared nodes to a namespace do not see each other, also to match Tailscale.com behaviour:

Company A has two shared nodes from Company B and Company C. It would not be very nice if B and C are able to see each other :)

I am afraid this is one of this Working As Intended™ cases.

@juanfont commented on GitHub (Oct 30, 2021): Shared nodes do not expose their subnets, to match the behaviour Tailscale.com has (https://tailscale.com/kb/1084/sharing/#sharing--subnets-subnet-routers) And shared nodes to a namespace do not see each other, also to match Tailscale.com behaviour: > Company A has two shared nodes from Company B and Company C. It would not be very nice if B and C are able to see each other :) I am afraid this is one of this Working As Intended™ cases.
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
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#66
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?