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

Auto-update blog content from Obsidian: 2025-10-12 13:49:47
All checks were successful
Blog Deployment / Deploy-Staging (push) Successful in 10s
Details
Blog Deployment / Test-Staging (push) Successful in 2s
Details
Blog Deployment / Test-Production (push) Successful in 2s
Details
Blog Deployment / Clean (push) Has been skipped
Details
Blog Deployment / Notify (push) Successful in 3s
Details
Blog Deployment / Check-Rebuild (push) Successful in 6s
Details
Blog Deployment / Build (push) Has been skipped
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 9s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-10-12 13:49:47 +00:00
parent 7416866cad
commit 0644be25dc
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/post/13-migration-opnsense-proxmox-highly-available.md
View File

@@ -75,3 +75,7 @@ After the installation of both OPNsense instances, I give to each of them their
- `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.
## 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.