-
Notifications
You must be signed in to change notification settings - Fork 0
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
private ap ipv6 prefix #48
Comments
not sure if we can actually do this since we will just get /44 from edis |
Not sure what you mean here. Do you want a distinct IPv6 prefix for each node? |
exactly. but i'm not sure if we can do that, considering we will get at most a /44 from edis. since for ra we'll need a /64 |
in principle, we could get allocations from RIPE, but i don't see that being necessary: a /44 still contains 2²⁰ = 1 048 576 separate /64s. if we ever get to 10k nodes I'll break out the champagne, let alone a million
Theoretically not necessary, but yes I'm probably the only person ornery-enough to bother with prefixes longer than /64 (and cackle when bad software gets reaaaally sad about it) |
gets announced via hna, new range for private ap ipv6 prefixes, something like /48
The text was updated successfully, but these errors were encountered: