docs: add "Overlapping IPs for Resources" how-to#828
Conversation
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds a new MDX guide for overlapping internal IPs and updates several navigation entries in ChangesOverlapping IPs guide and navigation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
efb929f to
2435099
Compare
Adds the how-to under the reorganized /use-cases/remote-access group (stacked on the Use Cases reorg). Walks through the decision ladder for two sites sharing one internal IP, ending with the per-site TCP proxy pattern on each routing peer.
2435099 to
cff5a56
Compare
Summary
New Networks use-case guide at
/manage/networks/use-cases/overlapping-ips-for-resources, plus its sidebar entry under Networks → Use Cases (after "Reach Services on the Routing Peer").The guide owns the overlapping-IPs problem end to end: it opens with the symptom and root cause (a shared address can only ever resolve to one site, single-winner route selection), then presents the fixes as a decision ladder in order of preference:
streamproxy on each site's routing peer, for reaching both sites at once when the devices can't run the clientIt also names the two paths that look right and aren't (the built-in Reverse Proxy and custom NAT remapping) and why.
Only the last rung gets the full how-to treatment: proxy bound to the peer's NetBird IP so each site is reached by its own peer name, least-privilege policies scoped to the proxy port, common nginx pitfalls (module missing, block placement, boot ordering, peer re-registration), an optional custom DNS zone with CNAME records for friendly per-site names, and honest limits (per-service cost, no automatic failover of the proxy path, LAN-side listener exposure, TLS name expectations).
Summary by CodeRabbit