Auto-update blog content from Obsidian: 2025-10-22 19:25:53
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 10s
Blog Deployment / Test-Staging (push) Successful in 2s
Blog Deployment / Merge (push) Successful in 7s
Blog Deployment / Deploy-Production (push) Successful in 10s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s

This commit is contained in:
Gitea Actions
2025-10-22 19:25:53 +00:00
parent f9d1260a28
commit 3247e5871c

View File

@@ -157,7 +157,10 @@ From `Firewall` > `Rules` > `pfSync`, I create a new rule on each firewall:
### Configure HA
The high availability in OPNsense is done at two main layers. The first is the firewall state layer, the synchronization is permanent. The second layer is the configuration (XMLRPC Sync). This part is not automatically sync
The high availability in OPNsense is done at two main layers. The first layer is the firewall state, the synchronization is permanent. The second layer is the configuration (XMLRPC Sync). This part is not automatically synchronized and must be done only from the master to backup.
The
#### Master
Next, I head to `System` > `High Availability` > `Settings`:
- **Master** (`cerbere-head1`):
- **General Settings**
@@ -169,7 +172,7 @@ Next, I head to `System` > `High Availability` > `Settings`:
- **Remote System Password**: `<password>`
- **Services to synchronize (XMLRPC Sync)**
- **Services**: Select All
- **Backup** (`cerbere-head2`):
#### Backup (`cerbere-head2`):
- **Synchronize all states via**: *pfSync*
- **Synchronize Peer IP**: `192.168.44.1`, the master node IP
⚠️ Do not fill the XMLRPC Sync fields on the backup node, only to be filled on the master.