From 0d25963f4f80ee57233e39a30825cfc21be6fefd Mon Sep 17 00:00:00 2001 From: Pavel Skuratovich Date: Wed, 24 Sep 2025 09:35:22 +0300 Subject: [PATCH 1/2] Fix the table with examples in Wireguard component --- content/components/wireguard.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/content/components/wireguard.md b/content/components/wireguard.md index 81bf736257..f347f4c0ed 100644 --- a/content/components/wireguard.md +++ b/content/components/wireguard.md @@ -156,16 +156,16 @@ Incoming connections are not affected by `netmask`. Let's explain with some examples: -| address | netmask | allowed ips | working outgoing connections | -| ------------ | ---------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | -| 172.16.0.100 | *omitted* or 255.255.255.255 | *omitted* or any other value | **none**, no routes are created | -| | 255.255.255.0 | *omitted* | only to `172.16.0.0/24` | -| | | - 172.16.0.0/24 - 192.168.0.0/24 - *any other* | and any other network will be outside `172.16.0.0/24` | -| | | - 192.168.0.0/24 | **none** because `192.168.0.0/24` is not part of `172.16.0.0/24` | -| 10.44.0.100 | 255.0.0.0 | *omitted* | to `10.0.0.0/8` network | -| | | - 10.44.0.0/16 - 10.10.0.0/16 | only to the networks in the allowed list because the netmask will route the whole `10.0.0.0/8` but wireguard allows only those two subnets | -| any | 0.0.0.0 | *omitted* | **any** | -| | | - 172.16.0.0/24 - 10.44.0.0/16 - 10.10.0.0/16 | to any network that is in the list of allowed IPs because the netmask will route any traffic but wireguard allows only its own list | +| address | netmask | allowed ips | working outgoing connections | +| ------------ | ---------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| 172.16.0.100 | *omitted* or 255.255.255.255 | *omitted* or any other value | **none**, no routes are created | +| 172.16.0.100 | 255.255.255.0 | *omitted* | to `172.16.0.0/24` network | +| 172.16.0.100 | 255.255.255.0 | `- 172.16.0.0/24`{{< break >}}`- 192.168.0.0/24`{{< break >}} *`- any other`* | only to `172.16.0.0/24` because `192.168.0.0/24` and any other network will be outside of `172.16.0.0/24` | +| 172.16.0.100 | 255.255.255.0 | `- 192.168.0.0/24` | **none** because `192.168.0.0/24` is not part of `172.16.0.0/24` | +| 10.44.0.100 | 255.0.0.0 | *omitted* | to `10.0.0.0/8` network | +| 10.44.0.100 | 255.0.0.0 | `- 10.44.0.0/16`{{< break >}}`- 10.10.0.0/16` | only to the networks in the allowed list because the netmask will route the whole `10.0.0.0/8` but wireguard allows only those two subnets | +| any | 0.0.0.0 | *omitted* | **any** | +| any | 0.0.0.0 | `- 172.16.0.0/24`{{< break >}}`- 10.44.0.0/16`{{< break >}}`- 10.10.0.0/16` | to any network that is in the list of allowed IPs because the netmask will route any traffic but wireguard allows only its own list | > [!NOTE] > Setting the `netmask` to `0.0.0.0` has the effect of routing From 4c87eeadb49d95516d9567136e5a861be91ed301 Mon Sep 17 00:00:00 2001 From: clydebarrow <2366188+clydebarrow@users.noreply.github.com> Date: Sat, 4 Oct 2025 12:23:30 +1000 Subject: [PATCH 2/2] Add break shortcode --- themes/esphome-theme/layouts/shortcodes/break.html | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 themes/esphome-theme/layouts/shortcodes/break.html diff --git a/themes/esphome-theme/layouts/shortcodes/break.html b/themes/esphome-theme/layouts/shortcodes/break.html new file mode 100644 index 0000000000..037e6453b9 --- /dev/null +++ b/themes/esphome-theme/layouts/shortcodes/break.html @@ -0,0 +1,5 @@ +{{/* + Shortcode: break + Output: Inserts
+*/}} +