Use port 48646 for gopher64#143
Merged
Merged
Conversation
Owner
|
To be honest I would've made the same mistake as you, haha. I would've used something like 64646. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
I messed up when I chose port 64000 for Gopher64. I didn't realize that ports 49152-65535 are used dynamically by system services. I realized this when I found that Chrome was using port 64000 on my system. Ports 1024-49151 are supposed to be for these kinds of services, so I chose 48646.
Related Issue
gopher64/gopher64#890
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):