professional-service-best-practices/professional-service
19
1
Fork 0
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions

feat/replace-pfsense-with-opnsense #29

Merged
mauritz.uphoff merged 3 commits from feat/replace-pfsense-with-opnsense into main 2026-05-27 08:01:11 +00:00
Conversation 2 Commits 3 Files changed 32 +55 -45
sven.schmidt commented 2026-05-27 06:42:20 +00:00
Owner
Copy link

Summary

This PR replaces the previous pfSense-based hub firewall setup with an OPNsense-based implementation.

The goal is to use OPNsense as the central firewall/router component for the hub networking setup while keeping the existing overall architecture and deployment flow intact.

Changes

  • Replaced pfSense references with OPNsense
  • Added/updated the OPNsense image handling
  • Updated the server resource naming and configuration for OPNsense
  • Adjusted related volume, network interface attachment and backup resources
  • Updated variable/output references where required
  • Kept the existing hub networking structure and Terraform module semantics

Motivation

OPNsense is used as the preferred firewall appliance going forward. This change aligns the infrastructure code with the new target architecture and removes the previous pfSense dependency.

## Summary This PR replaces the previous pfSense-based hub firewall setup with an OPNsense-based implementation. The goal is to use OPNsense as the central firewall/router component for the hub networking setup while keeping the existing overall architecture and deployment flow intact. ## Changes - Replaced pfSense references with OPNsense - Added/updated the OPNsense image handling - Updated the server resource naming and configuration for OPNsense - Adjusted related volume, network interface attachment and backup resources - Updated variable/output references where required - Kept the existing hub networking structure and Terraform module semantics ## Motivation OPNsense is used as the preferred firewall appliance going forward. This change aligns the infrastructure code with the new target architecture and removes the previous pfSense dependency.
sven.schmidt self-assigned this 2026-05-27 06:42:20 +00:00
mauritz.uphoff was assigned by sven.schmidt 2026-05-27 06:42:20 +00:00
sven.schmidt added 2 commits 2026-05-27 06:42:20 +00:00
adjusted from var.project id to local.hub_project_id
All checks were successful
Default CI / Check for Open TODOs (pull_request) Successful in 33s
Details
Default CI / Secret Scanner (TruffleHog) (pull_request) Successful in 1m5s
Details
Default CI / Pre-Commit Hooks (pull_request) Successful in 1m59s
Details
50b6092523
mauritz.uphoff commented 2026-05-27 06:54:57 +00:00
Owner
Copy link

Can you also rename the dir from pfsense to opnsense?

Can you also rename the dir from pfsense to opnsense?
sven.schmidt added 1 commit 2026-05-27 07:03:03 +00:00
chore: rename pfSense hub-and-spoke folder to opnsense-hub-and-spoke
All checks were successful
Default CI / Secret Scanner (TruffleHog) (pull_request) Successful in 1m12s
Details
Default CI / Check for Open TODOs (pull_request) Successful in 1m24s
Details
Default CI / Pre-Commit Hooks (pull_request) Successful in 4m58s
Details
e5af52e85d
sven.schmidt commented 2026-05-27 07:03:27 +00:00
Author
Owner
Copy link

@mauritz.uphoff wrote in #29 (comment):

Can you also rename the dir from pfsense to opnsense?

Done with latest commit

@mauritz.uphoff wrote in https://professional-service.git.onstackit.cloud/professional-service-best-practices/professional-service/pulls/29#issuecomment-406: > Can you also rename the dir from pfsense to opnsense? Done with latest commit
mauritz.uphoff merged commit 8d6501e44e into main 2026-05-27 08:01:11 +00:00
mauritz.uphoff deleted branch feat/replace-pfsense-with-opnsense 2026-05-27 08:01:12 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
mauritz.uphoff
sven.schmidt
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: professional-service-best-practices/professional-service#29
No description provided.
Delete branch "feat/replace-pfsense-with-opnsense"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?