sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-18 19:49:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: selective internal access behind an exit node (#953)

Browse Source 
* docs: add selective internal access behind an exit node use case

Documents the two-routing-peer architecture for combining an exit node
with access to specific internal resources only: a resource peer inside
the data center scoped by policies, and an exit node placed on a segment
with internet-only egress. Names the two shortcuts that do not achieve
this (Block LAN access only covers directly attached subnets; host
forward-chain firewall rules are superseded by NetBird's own allow
rules) and adds verification steps, including the netbird down
requirement when enabling Block LAN access over the CLI on a connected
peer. Cross-links from the routing peer concepts and from How Routing
Peers Work.

* docs: make the single-host example clearly outside the subnet resource

* docs: accept all blocked-connection results and scope the exit-node guarantee

* docs: vendor-neutral egress wording and verify bullet polish
This commit is contained in:
Jack Carter
2026-08-27 14:22:06 +02:00
committed by GitHub
parent e60f8e8c4d
commit 24ca4178e3
2 changed files with 56 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/manage/networks/how-routing-peers-work.mdx
+1 -1
View File
@@ -218,7 +218,7 @@ Specifics:
- Set a DNS server with match domain `ALL` to prevent DNS-based location leaks. Local DNS servers may not be reachable from the exit node in any case.
- The `0.0.0.0/0` route exposes any network the exit node can reach, including its local LAN, not just the internet.
For setup steps and ways to limit what the exit node exposes (Block LAN access, network isolation), see [Configuring Exit Nodes for Internet Traffic](/use-cases/remote-access/exit-nodes#routing-peer).
For setup steps and ways to limit what the exit node exposes (Block LAN access, network isolation), see [Configuring Exit Nodes for Internet Traffic](/use-cases/remote-access/exit-nodes#routing-peer). For combining an exit node with access to specific internal resources only, see [Selective Internal Access Behind an Exit Node](/use-cases/remote-access/exit-nodes#selective-internal-access-behind-an-exit-node).
## Observability and troubleshooting