Auto-update blog content from Obsidian: 2025-10-13 19:51:23
All checks were successful
Blog Deployment / Merge (push) Successful in 6s
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 3s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 2s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 2s
All checks were successful
Blog Deployment / Merge (push) Successful in 6s
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 3s
Blog Deployment / Deploy-Production (push) Successful in 9s
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:
@@ -167,4 +167,6 @@ In the section `System` > `High Availability` > `Status`, I can verify is the sy
|
||||
|
||||
### Firewall
|
||||
|
||||
Let's configure the core feature of OPNsense, the firewall.
|
||||
Let's configure the core feature of OPNsense, the firewall. Now I just have to configure the master, the replication will do the rest for me.
|
||||
|
||||
To begin I create an alias, in `Firewall` > `Aliases`, to regroup all my internal networks
|
||||
Reference in New Issue
Block a user