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

Auto-update blog content from Obsidian: 2025-10-17 18:53:28
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 10s
Details
Blog Deployment / Test-Staging (push) Successful in 2s
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 10s
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-10-17 18:53:28 +00:00
parent e55b24825f
commit 7083e449f3
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -232,6 +232,8 @@ Finally, I want to allow anything from my trusted networks. In `Firewall` > `Rul
| **Category** | Trusted | | **Category** | Trusted |
| **Description** | Trusted | | **Description** | Trusted |
Great, with these 3 rules, I cover the basic. The remaining rules would be to allow specific equipment to reach out to something else. For example my home assistant instance want to connect to my TV, both are on different VLAN, hence I need a rule to allow it. I won't cover that in this post.
### DNS ### DNS
For the DNS, I will use Unbound. It is a validating, recursive, caching DNS resolver built into OPNsense, which can: For the DNS, I will use Unbound. It is a validating, recursive, caching DNS resolver built into OPNsense, which can: