lwip: ipv6: Fix incorrect peer address. #16613
Merged
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.
Summary
For IPv6 UDP sockets, the peer address was previously defined as only the first four bytes of the IP address. For IPv6 addresses, this resulted in an incorrect address expressed as IPv4. For instance, receiving a packet via
::recvfromfrom'fe80::87:e7ff:fe48:629a'is returned as having a peer address of'254.128.0.0'Testing
I have tested this with a UDP-based IPv6 service using
::sendtoand::recvfrom, and the address are now returned correctly to Python.The underlying sockets function works correctly if provided the correct IPv6 addresses, so this doesn't affect the underlying socket interface. Here is an example echo service which doesn't work with the current implementation:
Trade-offs and Alternatives
This uses slightly more memory for IPv4 UDP socket servers as memory is allocated based on the largest supported address family. However, it's only a few bytes per function call.