Skip to content

docs(pong): document valid port range (1-65535) for Property.port and Peer.port - #57

Merged
davvd merged 1 commit into
APN-Network:masterfrom
VasilevNStas:28-docs/port-range
Jul 4, 2026
Merged

docs(pong): document valid port range (1-65535) for Property.port and Peer.port#57
davvd merged 1 commit into
APN-Network:masterfrom
VasilevNStas:28-docs/port-range

Conversation

@VasilevNStas

Copy link
Copy Markdown
Contributor

Description

Documents the valid TCP port range (1–65535) for both Property.port and Peer.port. No wire changes.

Problem

Both port fields are uint32 (proto3 has no uint16), accepting values up to 4,294,967,295. A value above 65535 causes the client TCP dial to fail with a platform-specific "invalid port" error. Without documented bounds, neither the Hub nor the Node has a spec-level signal to reject out-of-range values.

Changes

  • Property.port: added "Valid range 1–65535; the Hub and Node MUST reject values outside this range."
  • Peer.port: added "Valid range 1–65535; the Hub MUST reject values outside this range."

Closes #28

@VasilevNStas

Copy link
Copy Markdown
Contributor Author

@davvd @yegor256 please review PR

@davvd
davvd merged commit 103e01a into APN-Network:master Jul 4, 2026
@0crat

0crat commented Jul 4, 2026

Copy link
Copy Markdown

@VasilevNStas Thanks for the contribution! You've earned +8 points for this: +16 as a basis; -8 for too few (6) hits-of-code. Please, keep them coming. Your running score is +84; don't forget to check your Zerocracy account too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Property.port and Peer.port use uint32, allowing values above 65535 that no TCP stack accepts

3 participants