-
Notifications
You must be signed in to change notification settings - Fork 2k
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
gnrc_ipv6_ext_frag: Initial import of IPv6 fragmentation #11623
Conversation
3efab1a
to
cb5861f
Compare
Rebased to current master. This PR now doesn't have any dependencies anymore (but still remains WIP) |
9cdeccd
to
d394359
Compare
There is one test I'd like to add (test if forwarding a large packet does not cause refragmentation), but that can also be done as a follow-up if time presses => removing WIP. |
3051fd9
to
3d54070
Compare
release status ping, should I change the milestone? |
Isn't the (soft) feature freeze still a few weeks ahead? |
Yup, the 28th. Just a ping for those who mentioned they wanted this in. |
@cgundogan ping 👿 |
Since I still want to implement a test case for this, I'd prefer to have reassembly (#11596) be reviewed and merged first. It also makes more sense IMHO to first support the receiving end. |
This is now finally done. |
4ee0591
to
7e0024e
Compare
Rebased to current master to adapt for #11668. |
When you rebase please just squash those fixups directly. |
23722e3
to
f6d51b8
Compare
Rebased and squashed (I hope I disentangled this knot correctly... the tests are passing on |
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.
At a first glance this looks good too - I would enjoy more documentation though.
I don't know much about IPv6 fragmentation, so maybe by the time I understand it, it's well documented 😉
Addressed review comments |
Adapted tests, as ethos is perfectly fine sending huge fragmented packets, but still looses packets when receiving. |
Added boards to |
Murdock is only complaining about fixup commits (and their summary lengths). |
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.
I think I see what's going on now - but nothing more to comment on. Please squash.
Tests run on native
and ek-lm4f120xl
with ethos
. I would like to try this with real 802.15.4 hardware, but I'm not in the office again before next week and don't really expect any surprises other than driver bugs.
Reassembly is the more critical path anyway.
If the module is not used, nothing changes, so no potential for regressions.
Can you please create an issue for the ethos
bug, so we don't lose track of that? If you do, reference it in a comment for the unit test also, just squash directly.
Squashed |
48463c2
to
e62bb9c
Compare
Will do in a moment ;-) |
Thanks for the reviews. The requested issue you can find at #12264. |
Good to have this feature in one piece for the 2019.10 release! |
Most definitely! :-) |
Contribution description
This provides IPv6 fragmentation for GNRC. Reassembly was introduced in #11596 but that PR is independent from this one (though it touches similar files).
Testing procedure
Will provide tests, but
and sending large (> 1500 bytes) UDP packets to the host's TAP bridge works (ping does not work as reassembly is provided in a separate PR: #11596).
Issues/PRs references
Addresses #5371 in part.
Depends on
#11593and#11622.Touches similar files as #11596 but can be merged independent.