Document static peer ports for site-to-site firewall rules - #948
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Warning Review limit reachedNext included review available in 48 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
SunsetDrifter
force-pushed
the
cc/static-peer-ports
branch
from
August 24, 2026 14:26
855a72e to
288a048
Compare
Branch offices with strict egress policies need stable outbound rules toward main locations. Documents pinning --wireguard-port per peer plus a static DNAT at the main site, with the no-inbound trade-off stated and scoped, and cross-links from Incoming ports and the relayed- connections troubleshooting note.
SunsetDrifter
force-pushed
the
cc/static-peer-ports
branch
from
August 25, 2026 10:16
288a048 to
fad6f2f
Compare
SunsetDrifter
marked this pull request as ready for review
August 25, 2026 10:18
lixmal
approved these changes
Aug 25, 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.
What
Adds a "Static peer ports for site-to-site firewall rules" section to Ports & Firewalls, answering a recurring customer question: branch offices with strict egress policies need firewall rules toward main locations that stay valid, but the remote port shown in the ICE candidate endpoints is a dynamic NAT mapping and can be reassigned.
How
The section explains why the observed remote port must not be used in firewall rules, then gives an outbound-first recipe:
netbird up --wireguard-port), allocated from a range sized up front.A scoping note keeps the pattern narrow: controlled sites only, not for roaming devices, and not a general fix for relayed connections.
Also: