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 Request: Random IP Address Assignment #370

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

Originally created by @aadityabhatia on GitHub (Nov 15, 2022).

Feature request

Headscale assigns IP addresses from the configured range in a sequential order. Requesting an option to assign IPs randomly from the range.

Rationale: From a security perspective, random IP assignment typically makes it harder for a potentially compromised device to sequentially scan the network range or guess the other machines' IP addresses. For example, an IPv6 /48 subnet makes it nearly impossible to conduct a network scan. Several DHCP servers also assign IP addresses randomly for various reasons as well.

Originally created by @aadityabhatia on GitHub (Nov 15, 2022). # Feature request Headscale assigns IP addresses from the configured range in a sequential order. Requesting an option to assign IPs randomly from the range. Rationale: From a security perspective, random IP assignment typically makes it harder for a potentially compromised device to sequentially scan the network range or guess the other machines' IP addresses. For example, an IPv6 /48 subnet makes it nearly impossible to conduct a network scan. Several DHCP servers also assign IP addresses randomly for various reasons as well.
adam added the enhancementgood first issue labels 2025-12-29 01:27:51 +01:00
adam closed this issue 2025-12-29 01:27:52 +01:00
adam commented 2025-12-29 01:27:53 +01:00
Author
Owner
Copy Link

@aadityabhatia commented on GitHub (Feb 23, 2023):

Anything I can do to help move this along?

@aadityabhatia commented on GitHub (Feb 23, 2023): Anything I can do to help move this along?
adam commented 2025-12-29 01:27:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 28, 2023):

This issue is stale because it has been open for 180 days with no activity.

@github-actions[bot] commented on GitHub (Sep 28, 2023): This issue is stale because it has been open for 180 days with no activity.
adam commented 2025-12-29 01:27:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 13, 2023):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Oct 13, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
adam commented 2025-12-29 01:27:53 +01:00
Author
Owner
Copy Link

@aadityabhatia commented on GitHub (Oct 13, 2023):

This would have been a great addition to headscale. Is there a way to keep this issue open until actually resolved?

@aadityabhatia commented on GitHub (Oct 13, 2023): This would have been a great addition to headscale. Is there a way to keep this issue open until actually resolved?
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 good first issue
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#370
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?