starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-13 12:50:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Feature] migrate node #744

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

Originally created by @lovitus on GitHub (Jul 15, 2024).

Use case

Hello dear author
I have batch of nodes need to get deleted .(my server provider cuts the services.)
How could I reuse all the assigned ips to my new servers? (delete old nodes , then assign the ips to new servers)

Description

  • delete old nodes , reuse the ips for new nodes

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 @lovitus on GitHub (Jul 15, 2024). ### Use case Hello dear author I have batch of nodes need to get deleted .(my server provider cuts the services.) How could I reuse all the assigned ips to my new servers? (delete old nodes , then assign the ips to new servers) ### Description - delete old nodes , reuse the ips for new nodes ### Contribution - [X] I can write the design doc for this feature - [X] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancementstale labels 2025-12-29 02:23:09 +01:00
adam closed this issue 2025-12-29 02:23:09 +01:00
adam commented 2025-12-29 02:23:09 +01:00
Author
Owner
Copy Link

@mitchellkellett commented on GitHub (Jul 20, 2024):

I haven’t tried this personally. But backfillips may work for you. Alternatively you could perform an UPDATE statement on the DB.

@mitchellkellett commented on GitHub (Jul 20, 2024): I haven’t tried this personally. But `backfillips` may work for you. Alternatively you could perform an UPDATE statement on the DB.
adam commented 2025-12-29 02:23:10 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Sep 8, 2024):

How could I reuse all the assigned ips to my new servers? (delete old nodes , then assign the ips to new servers)

I'm not sure if I understand your question in full, please consider carefully.

By default, Headscale assigns IP addresses sequentially. If you currently do not have any holes in your IP address assignment, the following should work (did something similar on 0.22.x):

  • Delete a node from headscale
  • There is now a hole somewhere in the middle in your range of assigned IP addresses
  • Register the "same" node with headscale
  • The previously removed IP addresses should be picked up by the new node
@nblock commented on GitHub (Sep 8, 2024): > How could I reuse all the assigned ips to my new servers? (delete old nodes , then assign the ips to new servers) I'm not sure if I understand your question in full, please consider carefully. By default, Headscale assigns IP addresses sequentially. If you currently do not have any holes in your IP address assignment, the following should work (did something similar on 0.22.x): * Delete a node from headscale * There is now a hole somewhere in the middle in your range of assigned IP addresses * Register the "same" node with headscale * The previously removed IP addresses should be picked up by the new node
adam commented 2025-12-29 02:23:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 26, 2024):

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

@github-actions[bot] commented on GitHub (Dec 26, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:23:10 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 2, 2025):

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

@github-actions[bot] commented on GitHub (Jan 2, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 stale
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#744
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?