Any help with installing in a Hyper-V environment?
iomega311 last edited by
I have a Windows 10 machine with multiple Linux servers running in a Hyper-V environment. I have an Intel dual gigabit NIC installed that I added specifically for pfSense.
I would like to have pfSense running as a Hyper-V VM along side my other VM's. I also want to have all of my physical machines behind pfSense as well.
My plan is to connect my modem directly to one port on my dual NIC, and have an external virtual switch tied to that as my WAN.
Then, to run ethernet from the other port on my dual NIC to a physical switch and have an interl virtual switch tied to that as my LAN.
I was able to setup pfSense in Hyper-V with legacy network adapters with WAN set to de0 and LAN set to de1. I was able to get an IP for my WAN, and set one for my LAN. However, none of my VMs or physical machines were able to get out to the internet. Not only that, but I was not able to get gigabit speeds… only fast ethernet. I am assuming this is due to using the legacy network adapters. :/
I then shut that machine down, created a second one, and with this one I used the standard network adapters instead of the legacy. And I cannot get pfSense to recognize any adapter. I thought that 2.2.x was suppose to be compatible with the standard network adapters in Hyper-V?
Any suggestions or tutorials out there on setting up in Hyper-V on 2.2.x? I can't run it if I cannot have gigabit speeds. Furthermore, I couldn't even get any of my hosts to get to the internet once I had it all set up.
Any help at all would be so wonderful.
ikkuranus last edited by
I have pfsense 2.2.4 installed on hyper-v windows 10 and it works fine with the normal adapters. Their isn't any steps that would prevent the normal adapters from showing up.
Gimli last edited by
Same here. Running 2.2.4 with standard adapters and it's working very well, and getting gigabit speed.
Just to rule out configuration error delete both virtual machines and all vSwitches then start from scratch with virgin images.
messerchmidt last edited by
if using same in a windows 10 hyper v, are there any limitations on using pfsense as a dhcp given the concurrent connection limitations of windows 10 (non-server)?