From 9578f503be4e2934e62a0304b6978d345d12bb29 Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Thu, 11 Sep 2025 07:01:31 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-09-11 07:01:31 --- content/post/11-opnsense-virtualizaton-highly-available.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/post/11-opnsense-virtualizaton-highly-available.md b/content/post/11-opnsense-virtualizaton-highly-available.md index 5e4d8a9..c38fc28 100644 --- a/content/post/11-opnsense-virtualizaton-highly-available.md +++ b/content/post/11-opnsense-virtualizaton-highly-available.md @@ -35,4 +35,8 @@ The layout changed a little since the OPNsense crash, I dropped the LACP link wh As I said in the intro, the plan is simple, replace the OPNsense box by a couple of VM in Proxmox. Basically, I will plug my ISB box directly to the main switch, but the native VLAN will have to change, I will create a VLAN dedicated for my WAN communication. -The real challenge will be located on the Proxmox networking \ No newline at end of file +The real challenge will be located on the Proxmox networking, with only one NIC to support communication of LAN, WAN and even cluster, all of that on a 1Gbps port, I'm not sure of the outcome. + +### Proxmox Networking + +My Proxmox networking is quite dumb, I only configured the network on each nodes, not at the cluster level \ No newline at end of file