-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After adding IPv6 prefix in config, existing machines don't get IPv6 addresses #614
Comments
This highlights a couple of other issues as well, since the IP is only given when a node joins, it will not update if the user:
Not sure yet what would be the best approach. We could;
|
So this also means that when IPv6 is removed, it will still show an IPv6 address for nodes that have registered before the change... and probably also when the range changed? |
This issue is stale because it has been open for 90 days with no activity. |
Ping.
|
I've given this some thought, and it is definitively possible to do this now with the new allocator, what I am unsure about is "when" to do it, I first thought about it as a check every time we load a node, but it has a lot of sharp edges, both resource and what if:
What I am leaning towards is having a "back fill based on current setting function" that can be called via CLI/API, and nothing automatic. So if you have ipv4, and add ipv6, this func will iterate over all machines and add ipv6 if its missing. or if you have both and remove ipv6, it will iterate over and remove all ipv6 addrs. Yes it is a manual step, but this should be something needed on only rare occasions? |
Updates juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Updates juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Updates juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Fixes juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Fixes juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Updates juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Fixes juanfont#614 Signed-off-by: Kristoffer Dalby <[email protected]>
Configuration without any prefixes defined, thus using only the default
100.64.0.0/10
. A few machines connected. Added IPv6 prefix (shown in examplesfd7a:115c:a1e0::/48
), restarted headscale. Even after restarting their services, existing machines did not get IPv6 addresses, that required removing them from headscale and adding anew.Context info
The text was updated successfully, but these errors were encountered: