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

sys/net/routing/ng_rpl: Add default case for missing OCP implementation #2

Conversation

jnohlgard
Copy link

It used to crash when receiving a MRHOF RPL message when only OF0 is implemented.

@jnohlgard
Copy link
Author

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 {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style

@cgundogan
Copy link
Owner

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

@jnohlgard
Copy link
Author

@cgundogan could you adapt and incorporate that in your big initial ng_rpl PR? (dropping the packet)

@cgundogan
Copy link
Owner

Sure, but please address the styling issue (line break before else)

@jnohlgard jnohlgard force-pushed the spr/cgundogan/ng_rpl_fib/rpl-ocp-default branch from abb8c60 to 2a8580e Compare July 21, 2015 11:52
@jnohlgard
Copy link
Author

rebased and addressed else newline comment, immediately squashed

cgundogan added a commit that referenced this pull request Jul 22, 2015
…fault

sys/net/routing/ng_rpl: Add default case for missing OCP implementation
@cgundogan cgundogan merged commit b9cd22a into cgundogan:ng_rpl_fib Jul 22, 2015
@jnohlgard jnohlgard deleted the spr/cgundogan/ng_rpl_fib/rpl-ocp-default branch September 21, 2015 06:56
cgundogan pushed a commit that referenced this pull request May 27, 2019
…onal

sys: make uart_stdio RX optional (attempt #2)
cgundogan pushed a commit that referenced this pull request Aug 21, 2019
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.
cgundogan pushed a commit that referenced this pull request Feb 9, 2022
The ENTROPY test always fails on this board

main(): This is RIOT! (Version: buildtest)
mbedtls test

  SHA-224 test #1: passed
  SHA-224 test #2: passed
  SHA-224 test #3: passed
  SHA-256 test #1: passed
  SHA-256 test #2: passed
  SHA-256 test #3: passed

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

Successfully merging this pull request may close these issues.

2 participants