Support fixed bridge port ranges#78
Merged
Merged
Conversation
Allow deployments behind firewalls to constrain bridge TCP listeners to a configured range while preserving ephemeral defaults.
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
1 participant
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
Adds firewall-friendly TCP bridge port configuration for Subspace servers. Operators can now constrain bridge listener allocation to a fixed port or inclusive range with
--bridge_ports=PORTor--bridge_ports=START-END, while preserving the existing ephemeral-port default.The same allocator is used for subscriber-side bridge listeners and reliable-channel retirement listeners. If a configured range is unavailable,
--bridge_ports_fallback_ephemeralcontrols whether setup falls back to an ephemeral port or fails closed.Test Plan
bazelisk test //client:bridge_test