-
Notifications
You must be signed in to change notification settings - Fork 2k
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
gnrc_rpl: add netif_addr to DODAG #5136
Conversation
d680aa2
to
884663c
Compare
I'm not opposing, but when we use |
Hmm, I don't see the connection to ND here. There exists a |
884663c
to
b280984
Compare
rebased |
I mean |
I am not sure whether the valid lifetime is set through ND, but it is propagated in PIO which is used in ND, but also in RPL. So there is a common interest in these values even for RPL without ND |
AFAIU, the preferred and valid lifetime should be set when the ipv6 address is added to the interface. So this may set an administrator or whoever adds that ip address to the interface. RPL is just readeing those values and puts them into the PIO. |
Although, I think we currently do not support this and the lifetimes are infinite (: |
there is however one problem that we also have without this PR: If someone deletes the ipv6 address that is used for this DODAG (and with this PR, the same is true for the according |
Ok, looks good codewise 👍 |
we should open an issue for it |
works as expected so ACK |
I guess then we will get a nullpointer exception and/or corrupt the memory of others |
By storing the
netif_addr
in the DODAG we can omit values like theprefix_len
,preferred_lifetime
andvalid_lifetime
of the IPv6 address configured by RPL PIOs. No need to store the same information at several places.Depends on #5135