-
Notifications
You must be signed in to change notification settings - Fork 45
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
Version Number Modification Attack Report has wrong DODAG Graph in it? #33
Comments
Hi @mueller91 ! Thank you very much for this feedback. Your interpretation makes sense, I mean that it should have provided something different for the DODAG. |
Hi @dhondta thank you very much for your reply! I did run the test several times, the outcome looks similar in all cases. Please see, for example, report2.pdf, also created via |
Hi @mueller91 I just started a few simulations and that is kind of weird ; it's just like the Version Number Modification Attack had the effect of the Blackhole Attack... This requires further investigation as the ContikiRPL implementation could have been patched and the related attack building blocks could be obsolete. |
Can you provide me with the version of Contiki that you have been using when it worked? I really find your project useful and would like to help out finding the issue. |
This is difficult to say ; at the time of the academical project, I did not implement a functionality to check for the versions (of Contiki and the framework itself). So, I did not noted the version when the related attack simulation was run when it gave me the expected result. |
Without this, blocks such as '"rpl_recalculate_ranks();", null' are ignored. This also resolves issue dhondta#33, now the graphs are correct in all the reports.
I found that building blocks such as Check out my commit above. It's a quick hack, so feel free to re-implement it yourself. Also, the deletion of the vagrant file was a misclick. |
My gosh, I guess I could have used something less cute in the building-blocks' JSON in the version at the time when I made the academical report and that, afterwards, I made slight changes without figuring out I let something missing... Anyway, thank you so much for finding this. Please submit it as a Pull Request so that I can get it fixed in the master project. |
Dear all,
please look at the attached report.pdf, which i generated using
fab demo
. To me, it looks like the DODAG graph in the report is the one from the Blackhole Attack? You can see that after the attack, the malicious node is parent of a majority of the surrounding nodes.The text was updated successfully, but these errors were encountered: