firmware: fixed set ipv6 address conflicts between RPL, radio and border_router modules #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR has to the propose of fix the conflicts presents in ipv6 setup in each module reported in the issue #257, radio will be modify to work under the physical layer, rpl and border router could be needs the settings of ipv6 address, these needs to check if a global address already exists, if doesn't exist don't should be able to modify the ipv6 params.
Testing procedure
could add The basic modules as border_router and rpl in makefile
When these modules are added you could manage all the functions required from both elements.
add to .c
note : in case that you are running first
rpl_setup
before to theborder_router_add_ipv6
, you could see that the ipv6 address saved it's the ipv6 addres generated by the uniqueid module or property from cpuid.New features:
rpl_setup()
receives now a parameter to set in mode DAG or DODAG.Border_router_add_ipv6()
has a new param to set to a WIRELESS_INTERFACE or WIRED_INTERFACE an ipv6 address-Issues/PRs references
Fix #257