How syedhnaqvi/pfsense works
Project type and purpose
• This is a hands-on lab/tutorial showing how to deploy a pfSense firewall in a virtual environment (Oracle VirtualBox or VMware), configure multiple virtual network interfaces (WAN, LAN, DMZ), and connect a client VM to the LAN segment.
• It is not an application codebase but a deployment guide whose “architecture” is a segmented network.
File structure & README
• The README defines three network interfaces on the pfSense VM and a second VM (Ubuntu/Windows) on the LAN segment.
Main components
a. Hypervisor host (Oracle VirtualBox or VMware)
b. pfSense VM
• Network interface Adapter-1 → WAN (bridged or NAT to the internet)
• Adapter-2 → LAN internal network
• Adapter-3 → DMZ internal network
c. Client VM (Ubuntu/Windows) attached to the LAN network
d. External Internet (represented as a cloud)
Relationships and data flows
• Traffic from the Internet cloud enters Adapter-1 on the pfSense VM (WAN).
• pfSense enforces firewall rules to permit/deny/route traffic between WAN, LAN, and DMZ segments.
• LAN clients (the tutorial’s second VM) send outbound traffic via Adapter-2; pfSense NATs it to the WAN.
Key architectural patterns & principles
• Network segmentation: Separation of WAN, LAN, and DMZ.
• Single-point gateway: pfSense VM as central firewall/router.
• Virtualization: All components live as virtual machines on one hypervisor.
• Defense in depth: DMZ isolates public-facing services.
Technologies & tools to annotate
• pfSense CE (firewall OS)
• Oracle VirtualBox or VMware Workstation Player
• 7-Zip (for ISO extraction)
• Optional client OS label (Ubuntu or Windows)
6. A callout listing key tools: pfSense CE, VirtualBox/VMware, 7-Zip.