Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Nov 15, 2014

No description provided.

Adds an explanation to a non-obvious behaviour in the core client,
where non-standard ports are avoided unless the node is truly desperate
to find somebody who is still alive and willing to take their
connection. The original code comment describes the behaviour but not
the reasoning.

Fix typo.
@ghost ghost closed this Nov 15, 2014
laanwj added a commit that referenced this pull request Dec 17, 2020
…ng default ports

010eed3 doc: warn that incoming conns are unlikely when not using default ports (Adam Jonas)

Pull request description:

  Closes #5150.

  This was mostly copied from #5285 by sulks, who has since quit GitHub.

  The issue has remained open for 6 years, but the extra explanation still seems useful.

ACKs for top commit:
  laanwj:
    re-ACK 010eed3

Tree-SHA512: d240fb06bba41ad8898ced59356c10adefc09f3abb33e277f8e2c5980b40678f2d237f286b476451bb29d2b94032a7dee2ada3b2efe004ed1c2509e70b48e40f
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants