Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Inconsistent byte order handling in mptcpd was corrected. IP ports
sent in path management commands and events now have the correct
byte order. Furthermore, the mptcpd unit test suite no longer
assumes that the tests will be run on a little endian host. IPv4
addresses and IP ports used in the mptcpd unit test suite are now
byte swapped as needed according to the endianness of the platform.
As always, IPv4 addresses and IP ports passed through pointers to
struct sockaddr should be in network byte order by convention.
A potential memory violation caused when attempting to register NULL
networking monitoring operations with mptcpd was fixed.
Mptcpd now supports gcc 12. Link-time errors found in gcc 12 mptcpd
builds were fixed.
ELL 0.45 or greater is supported.
Code coverage was further expanded.
The mptcpd network monitor supports loopback interface monitoring if
so desired.
Improved support for reproducible builds by disabling HTML
timestamps in Doxygen generated mptcpd documentation.
Some mptcpd unit tests will be skipped rather than allowed to fail
on hosts running a kernel without MPTCP support.