Skip to content
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

Open
mkg20001 opened this issue Jan 17, 2023 · 4 comments
Open

private ap ipv6 prefix #48

mkg20001 opened this issue Jan 17, 2023 · 4 comments

Comments

@mkg20001
Copy link
Member

gets announced via hna, new range for private ap ipv6 prefixes, something like /48

@mkg20001 mkg20001 moved this to In Progress in FFGraz Gluon Firmware Feb 17, 2023
@mkg20001 mkg20001 moved this from In Progress to Todo in FFGraz Gluon Firmware Apr 22, 2023
@mkg20001
Copy link
Member Author

not sure if we can actually do this since we will just get /44 from edis

@nbraud
Copy link

nbraud commented Apr 28, 2023

Not sure what you mean here. Do you want a distinct IPv6 prefix for each node?
Presumably to announce for a LAN with non-OLSR devices ?

@mkg20001
Copy link
Member Author

mkg20001 commented Apr 28, 2023

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

@nbraud
Copy link

nbraud commented Apr 28, 2023

exactly. but i'm not sure if we can do that, considering we will get at most a /44 from edis.

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
... but even then, we can give out prefixes as requested, rather than give each device a /60 or something.

since for ra we'll need a /64

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants