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

Single UDP packet fragmentation #659

Open
telemetrix opened this issue Feb 28, 2022 · 1 comment
Open

Single UDP packet fragmentation #659

telemetrix opened this issue Feb 28, 2022 · 1 comment

Comments

@telemetrix
Copy link

telemetrix commented Feb 28, 2022

Hello, there is some way to read out in the lib the length of the COAP/LWM2M payload required for the single message?

We are implementing the lib where the external TCP/IP stack from the cellular module is used and some of the packets are coming to us fragmented. It generates the errors on Wakaama lib so maybe there is some way how to glue the fragmented packets into the single one or at least to how much data is still missed?

The same issue we can face when the two UPD packets are glued.

@boaks
Copy link

boaks commented Feb 28, 2022

Not sure, If I understand your issue.

For UDP RFC768 the length is encoded in the UDP header.
CoAP uses that length in the UDP header and don't add one on its own (CoAP over TCP does, but not over UDP). Usually the UDP stack only forwards a UDP message after reassembling, or at least, the information, if reassembling is required and fragments are missing is left to that IP-stack.

So, CoAP doesn't have that length, you need to search at your modems IP-stack.

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

No branches or pull requests

2 participants