Vezpi/Blog
1
0
Fork 0
Code Issues Pull Requests Actions Wiki Activity

Auto-update blog content from Obsidian: 2025-09-14 10:43:59
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 17s
Details
Blog Deployment / Build (push) Successful in 29s
Details
Blog Deployment / Deploy-Staging (push) Successful in 9s
Details
Blog Deployment / Test-Staging (push) Successful in 3s
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 9s
Details
Blog Deployment / Test-Production (push) Successful in 3s
Details
Blog Deployment / Clean (push) Successful in 3s
Details
Blog Deployment / Notify (push) Successful in 2s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-09-14 10:43:59 +00:00
parent 29b9af9085
commit 3144fd29f7
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
content/post/opnsense-virtualizaton-highly-available.md
View File

@@ -39,4 +39,7 @@ The real challenge will be located on the Proxmox networking, with only one NIC
### Proxmox Networking ### Proxmox Networking
My Proxmox networking is quite dumb, I only configured the network on each nodes, not at the cluster level My Proxmox networking was quite dumb until really recently. Initially I only configured the network on each nodes. In that [article]({{< ref "post/11-proxmox-cluster-networking-sdn" >}}), I configured my VLANs in the Proxmox SDN.
Additionally, I have to add extra VLANs for this project, one for the WAN and the other for pfSync