You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit b88fa0a added support for sending and receiving OTA messages larger than 65535 bytes, but the length processing of downstream and upstream packets did not change.
This patch allows you to prepend and remove length prefix frames for individual packet headers that are greater than 65535. Packets and headers are capable of being larger. We made a conscious decision not to increase the maximum supported length prefix frame size so not to change (break) the packet API. You can still add larger headers with or without your own larger length prefix frame.
You may have to modify how you are creating your packets if this is a problem.
so models that send/receive large OTA messages don't have to implement their own functionality and can have similar logic to the standard EMANE models.
frames.
Added DownstreamPacket prependLengthPrefixFramingLong method to
prepend a 4 byte length prefix frame.
Added UpstreamPacket stripLengthPrefixFramingLong method to strip and
return a 4 byte length prefix frame.
Reported-by: Tom Goff <https://github.com/tomgoff>
See #79
Commit b88fa0a added support for sending and receiving OTA messages larger than 65535 bytes, but the length processing of downstream and upstream packets did not change.
The attached patch allows sending and receiving downstream and upstream packets that are larger than 65535 bytes.
emane-downstream-upstream-packet-length.patch.txt
The text was updated successfully, but these errors were encountered: