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

FS#978 - netifd: support smaller ipv6 segments than /64 #5916

Open
openwrt-bot opened this issue Aug 24, 2017 · 0 comments
Open

FS#978 - netifd: support smaller ipv6 segments than /64 #5916

openwrt-bot opened this issue Aug 24, 2017 · 0 comments
Labels

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Aug 24, 2017

nwf:

netifd makes the assumption that ipv6 segments will never be any smaller than a /64; it quite often computes things like (1 << (64 - prefix->length)) which obviously won't work out very well when prefix->length > 64. (Incidentally, it looks like it's never been tested with prefixes larger than a /32, too, since things like "int32_t current = 0, asize = (1 << (64 - assign->length)) - 1;" will also not work out very well when assign->length <= 32.)

The Linux network stack itself is more than happy to operate with these smaller segments, and odhcpd happily hands out leases. I know SLAAC won't work on these segments, but that's no reason to keep netifd from believing in them, IMHO. As it stands, I have several interfaces configured that the ubus-centric tools refuse to believe are set up!

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

No branches or pull requests

1 participant