-
Notifications
You must be signed in to change notification settings - Fork 2.1k
tests/gnrc_ipv6_ext: port to scapy #10382
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
Conversation
ec1cafd
to
b262989
Compare
4e559a6
to
f1ad649
Compare
f1ad649
to
c15cecb
Compare
Rebased to current dependencies, finished up the work and moved the RPL SRH tests to #10392. No longer WIP. |
4289710
to
a153b45
Compare
Rebased to current dependencies and also applied some fixes for Arch. |
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
0244b71
to
029d96a
Compare
Rebased to current master and dependencies. |
Tested on |
@miri64 could you squash? |
(Codacy output can be ignored) |
Squashed |
874fb3f
to
70c9706
Compare
Squashed |
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.
ACK
Thank you! Just one more to go ;) |
Thanks for the review! :-) |
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
Contribution description
This ports the
tests/gnrc_ipv6_ext
(which are actually very simple tests forgnrc_rpl_ext
), to just test the extension header parser usingscapy
to generate the IPv6 packets containing the extension headers.TODOs:
BOARD_INSUFFICIENT_MEMORY
Testing procedure
Compile
tests/gnrc_ipv6_ext
and flash it to a board of your choice. Usesudo make test
to run (due to the required Ethernet frame construction with the tap interface you need root permissions).Issues/PRs references
Depends on #8594, #10242, and #10244 and their dependencies: