From ac4d3b9a45a3f303104f68a10d0cf6394d27bb18 Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Mon, 29 Sep 2025 12:46:07 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-09-29 12:46:07 --- .../post/12-opnsense-virtualization-highly-available.fr.md | 6 +++--- content/post/12-opnsense-virtualization-highly-available.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/post/12-opnsense-virtualization-highly-available.fr.md b/content/post/12-opnsense-virtualization-highly-available.fr.md index 3a451ad..1da34d8 100644 --- a/content/post/12-opnsense-virtualization-highly-available.fr.md +++ b/content/post/12-opnsense-virtualization-highly-available.fr.md @@ -1,7 +1,7 @@ --- slug: opnsense-virtualization-highly-available -title: Build a Highly Available OPNsense Cluster on Proxmox VE -description: A proof of concept showing how to virtualize OPNsense on Proxmox VE, configure high availability with CARP and pfSync and handle a single WAN IP. +title: Construire un Cluster OPNsense Hautement Disponible sur Proxmox VE +description: Une preuve de concept montrant comment virtualiser OPNsense sur Proxmox VE, configurer la haute disponibilité avec CARP et pfSync, et gérer une seule IP WAN date: 2025-09-29 draft: true tags: @@ -278,4 +278,4 @@ Cette preuve de concept démontre qu’il est possible de faire tourner **OPNsen Le résultat est à la hauteur : failover transparent, synchro des états, et connexions actives qui survivent à un crash. Le point le plus délicat reste la gestion du bail WAN, mais le hook CARP règle ce problème. -🚀 Prochaine étape : préparer la migration de mon réseau de production vers ce cluster HA virtuel, avec un minimum de coupures. Restez connecté ! \ No newline at end of file +🚀 Prochaine étape : préparer un nouveau cluster OPNsense HA sur Proxmox en vue de remplacer complètement ma box physique actuel. Restez à l'écoute ! \ No newline at end of file diff --git a/content/post/12-opnsense-virtualization-highly-available.md b/content/post/12-opnsense-virtualization-highly-available.md index beb80db..526c973 100644 --- a/content/post/12-opnsense-virtualization-highly-available.md +++ b/content/post/12-opnsense-virtualization-highly-available.md @@ -280,4 +280,4 @@ This proof of concept showed that running **OPNsense in high availability on Pro The setup behave exactly as expected, seamless failover, synchronized firewall states, and even live sessions surviving a node crash. The most delicate part was handling the WAN lease, since my ISP modem only provides one IP, but the CARP hook script solved that challenge. -🚀 The next milestone will be carefully planning the migration of my network into this virtual HA pair with minimal downtime, stay tuned! \ No newline at end of file +🚀 The next milestone will be to prepare a new OPNsense HA cluster with the aim to completely replace my current physical box. Stay tuned! \ No newline at end of file