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

fix(s2n-quic-transport): Unmap peer address when determining MTU probe size #1321

Merged
merged 13 commits into from
May 21, 2022

Conversation

WesleyRosenblum
Copy link
Contributor

@WesleyRosenblum WesleyRosenblum commented May 20, 2022

Description of changes:

I noticed that server and client MTU probes were of different sizes in our interop tests, the server being 20 bytes smaller than the client. This is due to the server listening on a dual-mode socket (IPv4 and IPv6). When calculating the MTU probe size, we were interpreting IPv4 addresses that had been mapped to IPv6 as IPv6 addresses, resulting in a smaller MTU probe. This change unmaps the peer address so that the MTU probe reaches its maximum allowed size when listening on dual-mode sockets.

Testing:

Added unit test

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@WesleyRosenblum WesleyRosenblum marked this pull request as draft May 20, 2022 21:53
@WesleyRosenblum WesleyRosenblum marked this pull request as ready for review May 20, 2022 21:55
@WesleyRosenblum WesleyRosenblum merged commit 88aa6a2 into main May 21, 2022
@WesleyRosenblum WesleyRosenblum deleted the WesleyRosenblum/mappedmtu branch May 21, 2022 01:40
camshaft added a commit that referenced this pull request Jun 3, 2022
camshaft added a commit that referenced this pull request Jun 3, 2022
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

Successfully merging this pull request may close these issues.

2 participants