PfSense for DHCP/DNS server configuration

StormseekerV · Jan 2, 2016, 9:23 PM

Hello all,

I’m hoping someone could assist me with my configuration. As such, I’m using my personal knowledge and information found on various posts to help accomplish this Lab but as such, I’ve been unsuccessful in setting up my workspace

Im currently trying to setup a Virtual Environment for testing purposes.

The current setup I'm hoping to achieve would be the following:
I'm using Windows Server 2012R2 with Hyper-V enabled
On this Server I have 4 VM’s running. 1 for pfSense, 1 for Windows server 2012R2 (used as a DC, DNS, and DHCP server) and 2 test PC’s. The 2 PC’s are to be on a separate VLAN. As such, I would like these PC’s to be able to connect to the internet and they should also be able to communicate with the domain controller.

My current issue is that my PC’s on Client VLAN receive an IP address from the DC but can’t go to the internet and can’t communicate with the DC. ARP –a shows nothing outside their broadcast domain. The Domain Controller can get to the internet but cannot communicate with the PC’s in the other VLAN.

This is the current setup im using:
I have the following VMs:

1x pfSense Firewall
o Version
 Latest version (2.2.6 built on Monday Dec 21 2015)
o 4 Virtual NICS
 1x NIC called WAN
• Virtual switch properties
o External Network
o Physical NIC reserved for this network only
• Outside interface connects to the Internet
• IP Address: 192.168.80.133
 1x NIC called LAN
• Virtual Switch properties
o Private Network
• Inside interface
• IP Address: 192.168.1.1/24
 1x NIC called Server
• Virtual Switch properties
o Private Network
o VLAN Identifier enabled and set to VLAN 10
• Inside interface
• IP Address: 192.168.10.1/24
 1x NIC called Client
• Virtual Switch properties
o Private Network
o VLAN Identifier enabled and set to VLAN 20
• Inside interface
• IP Address: 192.168.20.1/23
o DHCP functions disabled
 DHCP relay enabled on the following NICs:
• LAN
• Client
• Server
o Firewall rules on both the Server and Client NIC to permit all types of traffic
o DNS set to 192.168.10.10 (Windows Server 2012R2 set as a DNS server)
1x Windows Server 2012R2
o Following roles enabled
 DHCP
 DNS
 AD
o IP Address: 192.168.10.10 (Static)
2x PC ‘s
o Windows 8.1 and Windows 10
o IP Address: DHCP

If someone could point out some steps I may have missed or possibly what other configuration I would need to look at, it would be greatly appreciated.

Also, if you need any additional info, just let me know.

Thanks,

johnpoz · Jan 3, 2016, 12:58 AM

Why are you setting vlan tags on interfaces Are not tied to the physical world??

StormseekerV · Jan 3, 2016, 4:48 AM

True enough.

I removed the VLAN tags from the NICs and nothing seems to have changed.

I guess my problem is that the Windows Server 2012 box has no problems going onto the internet and the such. I assume this is because it has a DNS server it can reach (itself).

The PC's which are on the Client network card receives a DHCP assignment due to DHCP Relay but the PC cant seem to get past the initial gateway (192.168.20.1). I can ping the gateway but nothing beyond that.

Both the Server and Client NIC have a rule permitting Any to Anywhere so Im not sure why the communication isnt working. It may be a lack of proper routing but I'm still learning.

Thank you for the input.

johnpoz · Jan 3, 2016, 12:32 PM

there is no need to route between your segments… Unless you have set a gateway that would override the native routing of pfsense knowing it has those networks connected.

So you have 3 lan segments right, lan, server and client. And all the devices on these segments get dhcp from pfsense pointing to pfsense as gateway?? If they are getting dhcp from your 2k12 server that might be the problem.. You need to point them to the pfsense interface in each segment as there gateway. And yes you would have have to create firewall rules on the opt interfaces you enabled.

Post up your rules, and ipconfig /all from your devices..

StormseekerV · Jan 4, 2016, 1:50 AM

Thanks for the feedback so far, let me see how many of your questions I can answer :D

Here is the IPCONFIG -ALL of the Windows Server 2K12 on Server Segment and the PC on Client Segment:

Windows 8.1 PC on Client Segment
IP Address: 192.168.20.50
Subnet Mask: 255.255.254.0
DHCP Server: 192.168.10.10
DNS Server: 192.168.10.10
NetBIOS over TCPIP: Enabled
Default Gateway: N/A

Windows Server 2K12 on Server Segment
IP Address: 192.168.10.10
DCHP Enabled: No
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.10.1
DNS Server: 192.168.10.10
NetBios Over TCPIP Enabled

Firewall rule on both Client and Server segment:
IPv4 * * * * * *

So I think you nailed it when you mentioned that the PC on client segment isn't getting a Gateway. I didn't even notice it until you mentioned it.

Now the question would be, how do you get the DHCP from the Windows Server to assign proper gateways to computers on different segments.

Thanks,

johnpoz · Jan 4, 2016, 2:57 AM

Windows 8.1 PC on Client Segment
Default Gateway: N/A

How is going to go anywhere but its local network without a gateway????

And you sure you want a /23 mask?? Seems odd to be using /23 for a small couple of vms..

You put that in the dhcp options, which would be option 3 in this case

Here
http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml