aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--docs/netquirk.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/netquirk.md b/docs/netquirk.md
index b295b204..1fe2ad72 100644
--- a/docs/netquirk.md
+++ b/docs/netquirk.md
@@ -18,7 +18,7 @@ If an interface has only one peer, and that peer contains an Allowed IP in `/0`,
This prevents traffic from leaking outside the tunnel.
-If you'd like to use a default route _without_ having these restrictive kill-switch semantics, one may use the routes `0.0.0.0/1` and `128.0.0.0/0` in place of `0.0.0.0/0`, as well as `::/1` and `8000::/1` in place of `::/0`. This achieves nearly the same thing, but does not activate the above firewalling semantics. And users without the need for a `/0` route at all do not have to worry about this, and instead fall back to ordinary Windows routing and DNS behavior.
+If you'd like to use a default route _without_ having these restrictive kill-switch semantics, one may use the routes `0.0.0.0/1` and `128.0.0.0/1` in place of `0.0.0.0/0`, as well as `::/1` and `8000::/1` in place of `::/0`. This achieves nearly the same thing, but does not activate the above firewalling semantics. (The UI's editor has a checkbox that toggles this.) And users without the need for a `/0` route at all do not have to worry about this, and instead fall back to ordinary Windows routing and DNS behavior.
### Considerations for non-`/0` Allowed IPs