Windows users often set up their networks with VMware Workstation, which includes a pfSense virtual machine for firewalling and routing. While configuring the pfSense virtual machine, setting up LAN interfaces becomes an essential step. This article focuses on configuring pfSense LAN interfaces within VMware Workstation on a Windows host.
Prerequisites
Before proceeding, ensure the following prerequisites are met:
- A properly installed pfSense virtual machine using VMware Workstation on a Windows host.
- Basic knowledge of VMware Workstation and pfSense.
Configuring pfSense LAN Interfaces
The LAN interface in pfSense is typically the primary network interface that connects the firewall to the local network. By default, it is named "LAN." In VMware Workstation, the LAN interface is usually assigned to the virtual machine's first NIC.
Step 1: Edit pfSense Interface Configuration
Log in to the pfSense web interface using a web browser. Navigate to /interface in the URL. The Interfaces page appears, displaying the available interfaces.
Step 2: Assign IP Address and Subnet Mask
Click on the LAN interface. In the "IPv4 Configuration Type" dropdown, select "Static IP." In the "Address" field, enter the desired IP address for the LAN interface. In the "Subnet Mask" field, enter the subnet mask for the local network. Click "Save" to apply the changes.
Step 3: Configure VMware Workstation Virtual Machine NIC
In VMware Workstation, edit the settings of the pfSense virtual machine. Navigate to the "Network Adapter" tab and select the first NIC. Set the "Connection Type" to "Bridged" and choose the desired network adapter on the Windows host. Click "OK" to save the changes.
Step 4: Verify pfSense LAN Interface Configuration
In the pfSense web interface, navigate to /status>interfaces. The LAN interface's status and IP address should be displayed.
Configuring Additional pfSense Interfaces (OPT1, OPT2, etc.)
To configure additional interfaces, such as OPT1 or OPT2, follow the same steps as above, but assign different IP addresses and subnet masks within the same subnet.