Have you tried with different drivers versions for physical nic that you are using for Wan? IE the driver in the host operating system? In worst case it might even be worth to try another nic (If it doesn't do anything else it will rule out the nic as the cause)

are you on W10 pro or better? if so you got hyper-v available and in my eyes it's better for this jobb

Well.. I've found the problem, and boy do I feel stupid!  :-[ Turns out I hadn't allocated enough RAM to my Dom0. Whenever I launched the pfSense HVM, the Dom0 would run out of RAM and crash xl. Changed the allocation on the boot line from 256M to 2G, and it works beautifully.  8)

Thank you very much for the reply Migrating to 2012 R2 is not a valid option for me right now. I will continue searching for something or waiting for an update of the FreeBSD kernel in which pfSense runs  :-\

Does it start with 10.x.x.x, 192.168.x.x or 172.16-31.x.x ?? If so then its rfc1918..  Ie private IPs If it starts with pretty much anything else its public ;) See my wan is a public IP..  If you look up 24.13 its owned by comcast.. http://lmgtfy.com/?q=rfc1918 [image: wanpublic.png] [image: wanpublic.png_thumb]

I made some tests with Iperf and at first seems to be like gbit nic. Thanks for your help JorgeOliveira! :D

AWS has a Netgate official AMI.

"pfSense is currently based on FreeBSD 8.x." Huh??  That is OLD pfsense 2.3.3p1 is current running on freebsd 10.3-RELEASE-p17 https://www.freebsd.org/doc/handbook/disks-growing.html Simple enough to test this..  But since this is a VM.. Why don't you just fire up a new vm.. With the correct sized disk and partitions, etc.  Then restore your config to it..

I have the same configuration. Dual nic, both connected to virtual switches. The nic connected to the virtual lan switch is connected to a physical switch. The nic connected to the virtual wan switch is connected to a bridged port on the modem. The management interface for the hyper-v server is connected to the virtual lan switch.

Thank you for the reply and well structured response, But I might have been lost in the explanation correct me if im wrong, So in my case what im trying to do I have pfSense 2.2.6 virtual in Hyper V running windows 2012r2 server my window server has 3 physical NICS NIC1–-WAN NIC2---LAN ( which comes with the server) NIC3---EMAILIP  (Is my static IP for my email server) after that i add the virtual switch and then the virtual NIC to pfSense WAN LAN EMAILIP TEST NETWORK (This is what i want to VLAN) So in theory when I have installed VLANS on pfSense on bare metal i would add  a VLAN with the adapter of the LAN and the VLAN automatic goes though if the environment has a dumb switch. Now if it has a smart switch i have to TAG the ports (on where pfsense and unifi ap are connected)  on the smart switch depending on the VLAN i give and would work. But in this case when its virtual im somewhat stumped. I see you put a powershell example but you say "or" meaning i can do it though webgui instead? By any chance do you have an example on our hyper V? Thank you

I have a similar config (Lenovo i7). My pfSense VM boots in about 1min - turn on to menu. My VM is also v8 - Gen1 only 2 processors. pgk

First I would suggest that you use your Windows Domain Controller for DHCP / DNS - Windows Active Directory performs best when it "owns" everything with regards to names/dns etc.  If this is not the case many DNS servers don't post "all" the DNS records that AD likes to see-  this ends up with workstations having strange behavior - sometimes working - sometimes not. That said… I have several pfsense virtual machines running under hyper-v - the only "problem" that I may have encountered is using an SSTP VPN passing to the pfsense to the server (port forward) may have disconnect issues - I have not completely verified this but it is suspicious since my vpn works fine using the comcast gateway firewall/port forwards.  Strange that other https type traffic seems to work ok (remote desktop gateway).  Haven't had any other issues with pfsense in a VM. Install is just create a small VM - attach the pfsense install ISO and load as usual.  You will need to make sure of your network adapters (one on the internet and the other on the lan).  config and your good to go. regarding your dhcp question on your VMs:  If these are servers I would hope you are using static IPs for all your servers.  BUT - you can provide for a startup sequence in hyper-v - look at your VM settings - startup options - there is a delay that you can implement to have your VMs start in order on a timeline. pgk

I tried the second option but it didnt work for some reason. The first option did the magic. Added that property in the conf file, restarted pfsense. pfsense asked to configure new interfaces, The interfaces changed from xe to re. I reassigned the interfaces, boom - i have internet in the OPT1 interface  8)

perhaps you need to uncheck "Block private networks and loopback addresses ' on you pfsense wan interface?