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

Equipment insulation #443

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

Originally created by @Friedjof on GitHub (Mar 20, 2023).

Feature request

Currently, any device in the headscale VPN network can reach any other device. Now, however, this is not necessarily always desirable. Therefore, I would like to be able to define exactly which devices can see each other and which cannot. So perhaps one could create separate subnets for devices, whereby a device can also be in several subnets (with several IP addresses). This would allow Headscale to be used in a larger environment. Alternatively, one could of course also define who can see whom via a list. However, it would be more intuitive via subnets.

This structuring would specifically help me to include people from my circle of friends in my VPN and not directly release my entire network. It could also help to operate larger instances and shield individual users from each other.

Originally created by @Friedjof on GitHub (Mar 20, 2023). **Feature request** Currently, any device in the headscale VPN network can reach any other device. Now, however, this is not necessarily always desirable. Therefore, I would like to be able to define exactly which devices can see each other and which cannot. So perhaps one could create separate subnets for devices, whereby a device can also be in several subnets (with several IP addresses). This would allow Headscale to be used in a larger environment. Alternatively, one could of course also define who can see whom via a list. However, it would be more intuitive via subnets. This structuring would specifically help me to include people from my circle of friends in my VPN and not directly release my entire network. It could also help to operate larger instances and shield individual users from each other.
adam added the enhancement label 2025-12-29 01:29:26 +01:00
adam closed this issue 2025-12-29 01:29:27 +01:00
adam commented 2025-12-29 01:29:27 +01:00
Author
Owner
Copy Link

@madjam002 commented on GitHub (Mar 23, 2023):

You can do this with ACLs https://github.com/juanfont/headscale/blob/main/docs/acls.md

@madjam002 commented on GitHub (Mar 23, 2023): You can do this with ACLs https://github.com/juanfont/headscale/blob/main/docs/acls.md
adam commented 2025-12-29 01:29:27 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 10, 2023):

This is the intended behaviour, as @madjam002 points out, ACLs would be the desired solution for this.

@kradalby commented on GitHub (May 10, 2023): This is the intended behaviour, as @madjam002 points out, ACLs would be the desired solution for this.
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
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#443
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?