feat(gateway): support multi-port TCP listening via port ranges #489
+66
−20
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
Allow listen_port to accept either a single port (8443) or a range
string ("8443-8543") to bind multiple TCP listeners, avoiding
ephemeral port exhaustion under high connection counts.
Also removes the single-port field from HostInfo proto since
listen_port is now a range, and uses {e:#} for cleaner error logs.
kvinwang
force-pushed
the
feat/gateway-multiport
branch
from
276476e to
b325c0f
Compare
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.
Summary
listen_portto accept either a single port (8443) or a range string ("8443-8543") to bind multiple TCP listenersportfield fromHostInfoproto (no longer meaningful with port ranges){e:#}for cleaner connection error logsContext
Under high concurrency (>60K connections per port), a single listen port can exhaust its accept queue or cause kernel-level backlog issues. Binding multiple ports distributes incoming connections across more kernel data structures.
Load testing confirmed: 20 ports handled 200K concurrent TLS connections at 100% success rate.
Config example
Test results
listen_port = "14100-14110"/proc/net/tcp