From 65f4bc179453a04bda0baedc785e4b3e916e963a Mon Sep 17 00:00:00 2001
From: Gitea Actions <actions@local>
Date: Wed, 22 Oct 2025 19:38:15 +0000
Subject: [PATCH] Auto-update blog content from Obsidian: 2025-10-22 19:38:15

---
 content/post/13-opnsense-full-configuration.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/content/post/13-opnsense-full-configuration.md b/content/post/13-opnsense-full-configuration.md
index d7e9c50..2220560 100644
--- a/content/post/13-opnsense-full-configuration.md
+++ b/content/post/13-opnsense-full-configuration.md
@@ -57,13 +57,6 @@ Initially I was thinking of just restoring my current configuration on the VM fr
 
 Hopefully the next time, I will also cover the VM creation on Proxmox and how I'm preparing this migration from my physical OPNsense box to this highly available cluster in VMs. Let's dive in!
 
-TODO
-add section Topology
-add single WAN IP 
-add network diagram
-add IP/VLAN plan
-
-
 ---
 ## System
 
@@ -242,7 +235,7 @@ if ($type === "MASTER") {
 }
 ```
 
-In the Virtua
+In `Interfaces` > `Virtual IPs` > `Status`, I can force a CARP event by entering into `Persistent maintenance mode`. Triggering this allow me to test this script, which disable the WAN interface on the master while enabling it on the backup.
 
 ---
 ## Firewall