-
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
sys/net/routing/ng_rpl: Add default case for missing OCP implementation #2
sys/net/routing/ng_rpl: Add default case for missing OCP implementation #2
Conversation
but maybe dropping the packet is a better solution? |
ng_rpl_of_t *of = ng_rpl_get_of_for_ocp(byteorder_ntohs(dc->ocp)); | ||
if (of != NULL) { | ||
dodag->instance->of = of; | ||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style
IMHO ignoring these packets would be the proper way to handle this case. Otherwise, the rank value will have different meanings for nodes supporting the OCP and nodes not supporting the OCP |
@cgundogan could you adapt and incorporate that in your big initial ng_rpl PR? (dropping the packet) |
Sure, but please address the styling issue (line break before |
abb8c60
to
2a8580e
Compare
rebased and addressed |
…fault sys/net/routing/ng_rpl: Add default case for missing OCP implementation
…onal sys: make uart_stdio RX optional (attempt #2)
The evtimer_msg test is expanded to also delete entries. Furthermore the messages that are printed should now show numbers that are very close (if not equal). Something like this: At 740 ms received msg 0: "#2 supposed to be 740" At 1081 ms received msg 1: "#0 supposed to be 1081" At 1581 ms received msg 2: "#1 supposed to be 1581" At 4035 ms received msg 3: "#3 supposed to be 4035" The function evtimer_print is also called to show the intermediate status of evtimer entries.
It used to crash when receiving a MRHOF RPL message when only OF0 is implemented.