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.
High Level Overview of Change
Following up on #5290, this change sets the
[port_peer]
back to the legacy port 51235 rather than to the default port 2459.Context of Change
The config is part of the binary and, unless an explicit config is passed, the behavior of the binary will unexpectedly be different when the port changes. As the binary would then use a different port, it would possibly make the server inaccessible depending on how routes and firewalls are configured. To err on the safe side, this change restores the port to the legacy value as it was, but still recommends using the default port for new deployments.
Type of Change