From 0644be25dc245a9e1720a74c66059de1d92602b0 Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Sun, 12 Oct 2025 13:49:47 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-10-12 13:49:47 --- .../post/13-migration-opnsense-proxmox-highly-available.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/post/13-migration-opnsense-proxmox-highly-available.md b/content/post/13-migration-opnsense-proxmox-highly-available.md index 2ce8f5d..a696e4c 100644 --- a/content/post/13-migration-opnsense-proxmox-highly-available.md +++ b/content/post/13-migration-opnsense-proxmox-highly-available.md @@ -74,4 +74,8 @@ After the installation of both OPNsense instances, I give to each of them their - `cerbere-head1`: `192.168.88.2/24` - `cerbere-head2`: `192.168.88.3/24` -While these routers are not managing the networks, I give them my current OPNsense routeur as gateway (`192.168.88.1`) to able to reach them from my PC in another VLAN. \ No newline at end of file +While these routers are not managing the networks, I give them my current OPNsense routeur as gateway (`192.168.88.1`) to able to reach them from my PC in another VLAN. + +## Configure OPNsense + +Initially I thought about restoring my current OPNsense config on the VM, but as I didn't documented the first time, I take the opportunity to start over. \ No newline at end of file