From 5cbfca3b38f871ab6608eaef5b62ef75ad1e7fe9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marco=20Garc=C3=AAs?= <marco@garces.cc>
Date: Mon, 16 Dec 2024 12:42:19 +0000
Subject: [PATCH] adds small explanation to the routed subnet

---
 src/pages/how-to/manage-posture-checks.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/pages/how-to/manage-posture-checks.mdx b/src/pages/how-to/manage-posture-checks.mdx
index dc3d18f..8ba4935 100644
--- a/src/pages/how-to/manage-posture-checks.mdx
+++ b/src/pages/how-to/manage-posture-checks.mdx
@@ -193,5 +193,6 @@ When we are connected somewhere outside the office, we can observe:
 <p>
     <img src="/docs-static/img/how-to-guides/netstat-routes-grep-external.png" alt="high-level-dia" className="imagewrapper"/>
 </p>
+Notice that the subnet `192.168.1.0/24` is routed through our Wireguard interface (`untu100`).
 
 This concludes this Posture Check example.