Merge branch 'master' into elulcao/add-nokia-g240wb-router-guide

pi-hole · Oct 30, 2022 · be32fe2 · be32fe2
2 parents d20658d + f51abda
commit be32fe2
Show file tree

Hide file tree

Showing 5 changed files with 15 additions and 13 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -22,14 +22,14 @@ jobs:
           fetch-depth: 0
 
       - name: Set up Python
-        uses: actions/setup-python@v4.2.0
+        uses: actions/setup-python@v4.3.0
         with:
           python-version: "${{ env.PYTHON_VERSION }}"
           architecture: "x64"
           cache: pip
 
       - name: Set up Node.js
-        uses: actions/setup-node@v3.5.0
+        uses: actions/setup-node@v3.5.1
         with:
           node-version: "${{ env.NODE }}"
           cache: npm

diff --git a/docs/guides/vpn/wireguard/route-everything.md b/docs/guides/vpn/wireguard/route-everything.md
@@ -11,7 +11,9 @@ 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.
+    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](internal.md) 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:

diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -22,7 +22,7 @@
     "test": "npm run markdownlint && npm run linkinator"
   },
   "devDependencies": {
-    "linkinator": "^4.0.3",
+    "linkinator": "^4.1.0",
     "markdownlint-cli2": "0.5.1"
   }
 }
diff --git a/requirements.txt b/requirements.txt
@@ -1,5 +1,5 @@
 markdown-include==0.7.0
-mkdocs==1.4.0
+mkdocs==1.4.1
 mkdocs-git-revision-date-localized-plugin==1.1.0
-mkdocs-material==8.5.6
+mkdocs-material==8.5.7
 mkdocs-redirects==1.2.0