Add configurable WebRTC ICE port range - #376
Merged
rtm516 merged 3 commits intoJul 22, 2026
Merged
Conversation
Member
|
Just to note this will limit the number of users that can join to however many ports you have open |
Contributor
Author
|
Added a note in the config comment on the impact of a small range.
|
Updated comment for IcePortRange to improve clarity and conciseness.
rtm516
approved these changes
Jul 22, 2026
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
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.
NetherNet uses WebRTC, which gathers ICE candidates from the OS ephemeral port range by default. When running behind a firewall or in Docker with host networking, that forces opening a very large UDP range.
This adds an optional
session.ice-port-rangeconfig withmin/maxto pin the WebRTC ICE candidate ports: