PfSense & Server 2012 with Hyper-V guide

pfsense_Userz

I've read several posts already in regards to setting up pfsense in hyper-v / vmware but I'm not seeing any posts for a simple 2 NIC setup in a server 2012 Hyper-V VM

I read in one of the posts about some issue with networking in Hyper-V but had no further details. I have yet to find more on this.

What I am trying to do is setup a lab with server 2012 with Hyper-V s the host. The server has 2 NICs. Inside will be a VM for pfsense. (See image)

Setting up pFsense was pretty straight forward. However, the issue I have is that I'm confused over how to get my hyper-v server working on the network if pfsense is running over the wire.

My pfsense WAN ip is <isp managed="" ip="">and is running on NIC 1, LAN is 192.168.1.1 on NIC 2.

How do I configure the hyper-v server NICs? NIC 1 (WAN NIC in PFSENSE) will also be used on the server and thus try to obtain an IP from the ISP which it won't be able to (PPoE). Any issue with this?

NIC 2 (LAN NIC in PFSENSE) will be connected to the TPLINK router (since it will be a switch for my lan). This shouldn't cause any connectivity issues between the hyper-v server and pfsense, right?

Isn't there a in depth guide on this somewhere?

Thank you.

sample.jpg_thumb </isp>

chipbr

You are using Windows Server R1 or R2?

Anyway, no problem at all. Use NIC1 for WAN and NIC2 for LAN.

I recommend you to disable NIC1 virtual network (vnetwork on windows control panel) on the physical server, and let pfsense manage the PPPOE connection

pfsense_Userz

@chipbr:

You are using Windows Server R1 or R2?

Anyway, no problem at all. Use NIC1 for WAN and NIC2 for LAN.

I recommend you to disable NIC1 virtual network (vnetwork on windows control panel) on the physical server, and let pfsense manage the PPPOE connection

Thanks for the reply.

Server 2012 R1

I'll look into disabling virtual NIC on the host and see how that will work. In Hyper-V, I setup the NIC settings to have the Host OS share the VNIC. I'm guessing I need to disable it

hyper-v.JPG_thumb

chipbr

No need.
All my NICS have this option enabled.

paulsnoop

I've always assumed allowing the OS to share your WAN connection is a horrible idea, why would you ever want to do that?

chipbr

It depends on your network implementation.

This option makes the host acessible to the VM, through this connection. It has nothing to do with the WAN

See the help from Technet

The Allow management operating system to share this network adapter setting controls whether you can use this physical network adapter to access to the management operating system, which is operating system that runs the Hyper-V role. You can use this option to isolate the management operating system from communications between virtual machines and other computers on a physical network. However, this also means that you cannot connect to the management operating system remotely through this physical network adapter if this option is cleared.

https://technet.microsoft.com/en-us/library/cc754263(v=ws.11).aspx

bimmerdriver

We have three NICs. One for the WAN, one for the LAN and one is used to connect to the management interface of the modem. There are virtual switches on the WAN and LAN NICs plus an internal switch that's not connected to either NIC. The WAN switch is not shared with the OS. The LAN switch is shared with the OS. This allows there to be more than one instance of pfsense for testing. VMs can either connect to the LAN switch or with the internal switch (for testing).