Robert's Virtual

Building a Virtual Network - Part III

Putting together the virtual network

Since we are going to configure our firewall as the DHCP Server, we want to disable VMWare's DHCP server to avoid conflicts. Bring up a run dialog and type “services.msc”. Select “OK”. Scroll down and locate VMWare DHCP Service. Right-click and select Properties from the context menu. On the General Tab click the Stop button. To prevent the service from starting up with Windows change the startup type from Automatic to Disabled.
Stopping The VMWare DHCP Service
Disable DHCP Server

Next, Let’s force our bridged network, VMnet0, to only use our Internet capable adapter Go to “Start > Programs > VMWare > Manage Virtual Networks” (If using Vista, right-click and select “Run as Administrator” if UAC is enabled) Click on the “Host Virtual Network Mapping” Tab and from the dropdown in VMnet0, select the Internet-ready adapter. If you only have one physical NIC this is unnecessary.

Now we allocate the resources for our virtual machines and install them.

Recall that VMWare essentially takes memory from your host machine while your virtual machine is running. That being said, we need to lay out the resources we’re going to allocate to each virtual machine. My laptop has 3GB RAM. Here is what I came up with. Download the Specs.

Fischer (pfSense Firewall)
Hard Drive 2GB
      1 x Host-Only (LAN)
      1 x Bridged (WAN)
Euwe (Ubuntu Desktop)
Hard Drive 6GB
NIC – 1 x Host-Only
Kasparov (Ubuntu Server)
Hard Drive 4GB
NIC – 1 x Host-Only
Tal (Windows XP Pro)
Hard Drive 6GB
NIC – 1 x Host-Only
Lasker (Windows Server 2003)Hard Drive 8GB
NIC – 1 x Host-Only

Gather up all of your ISO's and dump them in the C:\Virtual Machines directory and configure your CD drive for to attach to the appropriate ISO when you create the machines.

Installing pfSense Firewall:
Create a VM for PfSense as demonstrated in Part I with the above specs and a Host-Only network adapter. the guest OS will be Linux Debian GNU/Linux 4 (32-bit). Add another network adapter configured as Bridged.
virtual pfSense 

Start your pfSense VM and when it boots from the ISO, allow it to boot to the default. At this time two NICs and their accompanying MACs should be identified. For my install the following were identified:
le0 = 00:0c:29:d8:b2:76
le1 = 00:0c:29:d8:b2:80

 We need to make sure we assign the correct NIC to the correct interface. Bridged to WAN and Host-Only to LAN. To match a MAC address with an interface we need to go back to the VMWare Console and select “Edit” from the drop down menu for Network Adapter 1. You can’t actually edit these settings while the VM is running, but you can view the MAC address and see that it’s a match for our Host-Only NIC (LAN).
firewall LAN WAN assignment
Assign NICs

Select "n" to VLAN configuration.
Enter the appropriate interface identifiers when prompted and hit Enter when finished. Review the information and enter “y” to confirm. Installation moves forward.

Once installation is complete, you’ll be presented with the pfSense base menu. This is where we’ll configure our LAN IP and DHCP scope.  Enter “2” to configure the LAN IP, enabling and configuring DHCP as well.
pfSense LAN configuration
pfSense LAN

The installation of our firewall is complete.

  • Create your other VM’s and Install your other OS’s
    • Windows Server 2003Ubuntu
    • Server 9.04 – Be sure to install LAMP
    • Ubuntu Workstation 9.04 (If you installed this in lab I, just change the NIC from NAT to Host-Only)
    • Windows XP Pro
  • Make sure fischer is running …it is our router and DHCP server after all.
  • Don’t forget to assign the correct hostnames!
  • It might be a good idea to update your OS’swith the lates service packs and patches
  • Remember to install VMWare Tools, you saw how to do this with Ubuntu ...Windows is pretty much automated.
  • You should be familiar with doing all of this.

System Updates
Use Windows Update for MS systems.
For Ubuntu machines run the following commands from a terminal

sudo apt-get update
sudo apt-get upgrade

At this point our firewall and all OS’s should be installed along with VMWare Tools. I chose not to install VMWare Tools on Ubuntu Server and pfSense as neither has a graphical interface.

Next we'll configure network settings on each VM and finish up configuration on the firewall.

1 2 3 4