VirtualBox, pfSense, Windows server 2012 wireless bridge setup

[IT-Student]

Hello folks,

I am struggling to get a virtual lab working for study.

Current Setup:
AMD x64 PC with single USB Wi-Fi adapter internet connection acting as Host.
VirtualBox 5
VM1 pfsense 2.2.3
VM2 Windows Server 2012 R2
VM3 Windows 7 Pro
Host LAN IP: 192.168.1.69
Gateway: 192.168.1.254

Objectives
VM's to be able to communicate with each other and reach the internet.
Windows Server will carry out DHCP, DNS roles etc

I have tried following with no success:

http://www.slideshare.net/rpainter/how-to-create-a-windows-server-2008-virtual-lab-using-virtualbox

I have followed the VB config and entered the exact same IP Address settings in the guide but my server and client machine cannot connect to the internet or communicate over the LAN.

Following the guide on P23 the DNS server IP address setting is a loop back address of 127.0.0.1.

Will this IP address work?
Or should this be set to 10.0.0.1 or 10.0.0.254?

Will I have to configure the DNS, DHCP server roles on the DC in order to get the connectivity working?

My host is connected to the internet using Wi-Fi, will setting adapter 1 to NAT in my pfsense VM work better?

Can anyone please assist with the correct IP addresses or setup?
I must explain I am completely new to networking and my knowledge is minimal.

Many Thanks

[KOM]

It's not that hard.  I don't have time to read that 20+ page spew you linked to but here how I do it in either VB or vmW:

Assumptions:  Your LAN is 192.168.1.0/24 with your router at 192.168.1.1

Create you pfSense instance with 3 NICs: WAN (bridged), LAN (Intnet1), DMZ (Intnet2)
For the WAN address, use a free IP address on your real LAN like 192.168.1.100
For the LAN & DMZ, give them private address in their own subnet (LAN 10.0.0.1/24, DMZ 10.0.1.1/24)
Enable DHCP on pfSense LAN and supply a pool range of 10.0.0.10-10.0.0.20
Create a vm with one NIC (Intnet1)
Use that VM to talk to the pfSense WebGUI at 10.10.0.1

[IT-Student]

Hi KOM,

Thanks for your input.
My Private IP is 192.168.1.69
Gateway: 192.168.1.254

I do not have the option of selecting DMZ for the 3rd adapter in the pfsense VM.

I'd rather get this working with only the 2 adapters tbh.
I have attached some screenshots of the settings I am using.

pfsense
Adapter 1 Bridged
Adapter 2 Internal

WAN DHCP: 192.168.1.81/24
LAN Static: 10.0.0.254/24

Now I have managed to get internet access on the VMs using the settings above but cannot get to the pfsense GUI at https://10.0.0.254 from within the internal network on the VMs?

Would you have any idea why please?

Many thanks


[KOM]

So what happens when you try?  Is there an error message?  Timeout?  I would expect you to get a client SSL warning.

[IT-Student]

When trying to access the GUI on the VM at 10.0.0.254 I just get this page cannot be displayed.
I also feel it would be better to have my windows server have AD assign DNS and DHCP together.
So I want to assign WAN a static IP address but when I try and do this I lose internet connectivity on the server VM.

pfsense WAN DHCP IP: 192.168.1.81 /24
I change this to static: 192.168.1.132 /24 (assumed this would be free to use)
Upstream Gateway: 192.168.1.1

I am not sure how to get the correct static WAN IP address settings.
My routers gateway address is 192.168.1.254 should I be entering that for the upstream gateway IP in pfsense?
How do I obtain the correct static WAN IP address settings in order for this to work please?

Many Thanks

[KOM]

My routers gateway address is 192.168.1.254 should I be entering that for the upstream gateway IP in pfsense?

Yes, 192.168.1.254 should be your pfSense WAN gateway.  In my example, I used 192.168.1.1 but I see how that would be confusing considering you already told me it was at .254 in your first post.

How do I obtain the correct static WAN IP address settings in order for this to work please?

If you're managing this network then that's the kind of thing you should already know ;) If you aren't the official network guy then you should ask him or he may get upset if you cause disruption.

That said, the first thing would be to check out your gateway's (.254) DHCP pool setting to make sure you aren't grabbing an IP address from the DHCP pool.  Then ping the address and see if you get a response – if not, use that IP address.  Not perfect but a start.  Is this a house or college dorm?  Do you know if any of the clients are static IP or not?  You can grab an address that seems to be unused but someone could turn on a device later on with the same static IP address.  Unlikely, but it happens.