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

Auto-update blog content from Obsidian: 2025-09-25 09:02:08
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Details
Blog Deployment / Build (push) Has been skipped
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 2s
Details
Blog Deployment / Clean (push) Has been skipped
Details
Blog Deployment / Notify (push) Successful in 2s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-09-25 09:02:08 +00:00
parent 95512dc407
commit ba4d20b861
3 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -176,11 +176,8 @@ I enable the interface on each instance and configure it with a static IP addres
- **poc-opnsense-1**: `10.103.0.2/24`
- **poc-opnsense-2**: `10.103.0.3/24`
On both instances, I create a firewall rule to allow communication coming from this network on that *pfSync* interface:
![opnsense-vm-firewall-allow-pfsync.png](img/opnsense-vm-firewall-allow-pfsync.png)
Then I configure the HA in `System` > `High Availability` > `Settings`, on the master (`poc-opnsense-1`) I configure both the `General Settings` and the `Synchronization Settings`. On the backup (`poc-opnsense-2`) I only configure the `General Settings`:
![opnsense-vm-high-availability-settings.png](img/opnsense-vm-high-availability-settings.png)
OPEN FIREWALL
OUTBOUND NAT ?