Some routers would block low number socket port #2249
Closed
Conversation
This file contains hidden or 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
When worked behind such a router, the tcp three-way handshake will fail due to the last ack message destined port 1024 blocked by router. So, when the board initiated a connection with a public server, using a bigger port number.
|
#2345 was just merged, which is essentially the same change but with a different port number based on IANA recommendations, so I'll close this one. Thanks, though! |
|
Okay, I feel sorry for not doing more research on this issue. |
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.
When worked behind such a router, the tcp three-way handshake will
fail due to the last ack message destined port 1024 blocked by router.
So, when the board initiated a connection with a public server, using
a bigger port number.