PfSense On Win10 Hyper-V With Ryzen 5 1600 and Dual Intel Pro 1000 NIC
Okay so I really want to get this working. Been fooling with it for the past week now, had it working last night but not how i wanted it or how its supposed to work "in my head". So here is the map im going for, im going to try to be as detailed and correct as i can be. Also note that the nic is a single intel pro 1000 card with two ports and then there is a built in nic on the motherboard.
Modem"issues ip via dhcp from isp to the router/firewall"–>WAN on pfSense VM"1st port on intel nic set up as external vswitch not shared with host OS"-->LAN on pfSense VM"2nd port on intel nic set up as internal to talk to host OS"-->Switch"theoretically this should go right to the switch"-->clients"including host OS through the built in nic"
Now this was working last night but heres the catch. For some reason the vLan hyper v switch and the actual "Lan, second port on that nic" show as two separate ports on the host machine. and I had to bridge them together in the host OS"win10" and have pfsense use that as the lan port? I guess lol. But more annoying is that the host is using that connection as its way to the wan. When i went to check active dhcp leases in pfsense the ip that the host had "192.168.1.115, it showed up as expired but online.
I dont really know what i did to make this work but it just did. I read some more stuff this morning and did some more diving, and noticed that 2.4.1 is out and allows hyper to run in gen 2 mode instead of gen 1 mode. I dont know if this is gonna help or not im going to check it out when i get home and see. I have verified that all my drivers work and that everything is up to date as well. So im certain its not any driver issues.
i just need a few questions answered and some feed back about this would be appreciated.
First question is. Is the map that im trying to create possible?
Second one is. Can that nic just be used by the Vm and not the host machine, I tried setting lan up as an external only not shared with host os and it wasnt working, or atleast how i set it up it wasnt. pfsense shouldnt have to go through the host os or have to get bridged to talk to that switch. it should just give an ip to that port which would be 192.168.1.1 and then go to the switch to hand out dhcp to the EAPs and hardwired devices.
Third question is would have I better luck using windows server and hyper v in that or is it just gonna be the same experience as win10 hyper v.
and finally is anyone else running a similar set up? the reason i have this set up and want to do this is because i want to be able to host game servers/other vms on this machine while running pfsense too. I dont want to have to use two machines "one for pfsense and one for vm stuff" if i can just do it all on one system and manage it from one machine it makes things so much simpler.
Thank you all.
I am running a similar setup. Message me on my channel if you have not figured it out yet. It took me a while to understand, but I know what you are after. https://www.youtube.com/channel/UCuGexDHQWBIqA1ThYKn0q9g?view_as=subscriber is my channel.
If you have a windows hyper-v server that you can run pfsense on, you should do that rather than use a desktop. I'm using a hyper-v server with multiple guests and it has been a stable configuration. I have two pfsense guests. One is for my physical LAN and one is completely virtual.