udp connect message use network endian #1564
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: yihuan.zhang <798528790@qq.com>
This was referenced Dec 6, 2023
|
Thanks for the PR! I chose to adopt a slightly different solution in PR #1468. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
base-commit:e3bdb5e27e03cf048ae584380448b358053fa2ca
when server and client run different endian machine in udp mode, then
unable to read from stream socketreturn.run client with -d, will get
Connect received for Socket 23, sz=4, buf=36373839, i=0, max_len_wait_for_reply=4.macro is in file
iperf.hlike#define UDP_CONNECT_REPLY 0x39383736.different endian cause iperf_udp_connect return error.