Hello everyone,
I hope you're all doing well. I'm reaching out for some guidance on a network project I've been working on.
Currently, my setup includes:
- OPNsense Firewall: This is running smoothly and is the primary gateway for my network.
- Proxmox Server: I'm in the process of integrating this. It has a single Ethernet port for network connectivity.
My primary goal is to deploy a Pi-hole instance on the Proxmox server. I'm still weighing whether to go with a Docker container or a standalone VM for this.
Here's the crux: My existing network devices operate in the 192.168.0.1xx IP range. I'd like the Pi-hole to be on a different subnet, specifically 192.168.33.xxx. This move is mainly for organization and segmentation purposes.
Considering the single Ethernet port on the Proxmox server and my intended setup, is this feasible? Moreover, are there specific challenges or configurations I should be aware of?
Any insights, advice, or shared experiences would be invaluable.
Thank you for your collective wisdom and time!
Uptate
so for all you people looking I managed to get it to work with this guide
Firewall Rules:
Allow Main LAN to Access the New Subnet:
Log into the OPNsense web interface. Go to Firewall > Rules > [LAN]. Click on the + button to add a new rule. Set the following:
Action: Pass
Interface: LAN
Protocol: Any (or you can specify TCP/UDP if needed)
Source: LAN net
Destination: Single host or alias and input 192.168.33.0/24.
Add a description (e.g., "Allow LAN to Access 192.168.33 Subnet"). Click Save.
Allow New Subnet to Reply (or initiate to the Main LAN):
- Go to Firewall > Rules > [Your VLAN interface, e.g., VLAN33].
- Click on the + button to add a new rule.
Set the following:
Action: Pass
Interface: [Your VLAN interface]
Protocol: Any (or you can specify TCP/UDP if needed)
Source: 192.168.33.0/24
Destination: LAN net
- Add a description (e.g., "Allow 192.168.33 Subnet to Access LAN").
- Click Save.
Apply Changes:
After creating the rules, click on Apply Changes to ensure the rules take effect.