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

Revert "Add --disable-default-route CLI flag documentation (#595)" (#601)

Browse Source 
This reverts commit 8ebe477d54.
This commit is contained in:
Maycon Santos
2026-02-14 16:33:25 +01:00
committed by GitHub
parent e3603aa4ee
commit 024ce42bfa
2 changed files with 0 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/manage/network-routes/use-cases/by-scenario/exit-nodes.mdx
-14
View File
@@ -93,20 +93,6 @@ Add a DNS server with the match domain set to `ALL`. Local DNS servers may not b
See [Manage DNS in your network](/manage/dns) for details.
## Disabling Default Route Installation
In some scenarios, you may want an exit node to be enabled on a peer without automatically routing all host traffic through the tunnel. For example, when you need custom policy-based routing or want to manage routes externally.
The `--disable-default-route` CLI flag prevents the default route (`0.0.0.0/0`) from being installed into the system routing table while preserving the WireGuard AllowedIPs configuration. This means WireGuard will still accept and encrypt traffic for all destinations, but the operating system won't automatically send all traffic into the tunnel unless your own routing rules direct it there.
```shell
netbird up --disable-default-route
```
<Note>
This flag only affects the system routing table. WireGuard AllowedIPs remain configured as usual, so traffic explicitly routed into the WireGuard interface will still be handled correctly.
</Note>
## High Availability
Exit nodes support high availability configurations. See [Creating Highly Available Routes](/manage/network-routes#creating-highly-available-routes) for more information.