pi-hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2024-12-06 19:27:12 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Emphasize that it is important to set up NAT of clients will show hard to debug network issues

Browse Source 
Signed-off-by: DL6ER <dl6er@dl6er.de>
This commit is contained in:
DL6ER
2022-10-28 18:54:27 +02:00
parent 84db3a9f9d
commit ff901228be
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/vpn/wireguard/route-everything.md
+2
View File
@@ -12,6 +12,8 @@ Rerouting the Internet traffic through your Pi-hole will furthermore cause all o
<!-- markdownlint-disable code-block-style -->
!!! warning "Ensure you're already forwarding traffic"
The following assumes you have already prepared your Pi-hole for [IP forwarding](internal.md#enable-ip-forwarding-on-the-server) and [enabled NAT](internal.md#enable-nat-on-the-server). If this is not the case, follow the steps over there before continuing here.
**If you haven't done this, your clients will apparently have no Internet connection whilst local connections may still work.** This is a hard to debug situation so please ensure you have everything set up to avoid hours of troubleshooting.
<!-- markdownlint-enable code-block-style -->
To route all traffic through the tunnel to a specific peer, add the default route (`0.0.0.0/0` for IPv4 and `::/0`for IPv6) to `AllowedIPs` in the `[Peer]` section of your clients's WireGuard config files: