Summary
It describes how to integrate and deploy PFsense in Machpanel Hyper-V environment.
Applies To
Applies to MachPanel build v 8.2.50 and above
Overview
This document outlines the prerequisites and key configuration requirements for deploying pfSense in a Hyper-V environment and integrating it with MachPanel. Adhering to these guidelines ensures consistency, scalability, and seamless operation, especially in high-availability (HA) setups.
1. PFSense Deployment on Hyper-V
2. Network Interface Configuration
- Configure network interfaces in pfSense as per deployment requirements.
- Maintain consistent interface naming and ordering across all pfSense instances (Primary and HA peers).
Important:
Consistent interface naming and ordering are critical for proper synchronization between pfSense nodes in high-availability configurations.
Reference Topology.
3. REST API Configuration (for MachPanel Integration)
4. Virtual Switch & Interface Alignment
- Ensure that the Hyper-V virtual switch name matches the corresponding pfSense interface name used for tenant communication.
- Recommended naming convention:
"TENANTS" (ensure correct spelling and consistency across all systems)
Important:
The naming must be identical across:
- Hyper-V Virtual Switch
- pfSense Interface
This is required for proper mapping and automation via MachPanel.
5. Trunk Configuration
- Configure the "TENANTS" virtual switch on Hyper-V as a trunk port.
- This allows multiple VLANs to pass through and enables tenant-level network segmentation.
6. High Availability Considerations
- For HA deployments:
- Apply identical configurations across all pfSense nodes.
- Ensure:
- Interface naming consistency
- Matching virtual switch configurations
- Proper synchronization settings
Failure to maintain consistency may result in sync failures or unpredictable behavior.