Hyper-V help
-
Hi all,
I'm trying to set up pfsense running inside Hyper-V, i previously had this running with a TP-Link wireless card as the NIC but recently that's decided to die on me so now i'm going down the hardwired route.
However since doing this i can't access the web configurator consistently, it sometimes happens and sometimes doesn't :-\ the PC I'm running it on only has one integrated NIC at the moment so I'm not expecting full functionality until my other NIC arrives but i should still be able to access the web configurator right? I can't access it from anything, even the machine that's running hyper-v :( and i have re-assigned the LAN to the wired NIC.
Also i obviously still want to be able to use my WiFi so I'll be using my DrayTek Vigor router as the AP and i also still want to run DHCP and my WAN off that too. is that still possible? I assume once my second NIC arrives I'll need to plug my Ethernet cables from the machine running pfsense into the LAN ports on the DrayTek and go from there?
Sorry if these questions are dumb but I'm no expert and I've been trying to figure out this problem for days now :(
As always thanks in advance!
-
Hi all,
I'm trying to set up pfsense running inside Hyper-V, i previously had this running with a TP-Link wireless card as the NIC but recently that's decided to die on me so now i'm going down the hardwired route.
However since doing this i can't access the web configurator consistently, it sometimes happens and sometimes doesn't :-\ the PC I'm running it on only has one integrated NIC at the moment so I'm not expecting full functionality until my other NIC arrives but i should still be able to access the web configurator right? I can't access it from anything, even the machine that's running hyper-v :( and i have re-assigned the LAN to the wired NIC.
Also i obviously still want to be able to use my WiFi so I'll be using my DrayTek Vigor router as the AP and i also still want to run DHCP and my WAN off that too. is that still possible? I assume once my second NIC arrives I'll need to plug my Ethernet cables from the machine running pfsense into the LAN ports on the DrayTek and go from there?
Sorry if these questions are dumb but I'm no expert and I've been trying to figure out this problem for days now :(
As always thanks in advance!
Are you attempting to run pfsense on a regular pc running hyper-v? If so, I'm not surprised you are struggling. Hyper-v works well, but not like this. (I have two pfsense guests on my hyper-v server.) This is not a recommended configuration. If you insist on running it on hyper-v, the computer should be server-grade and at a minimum, there should be dedicated nics for the wan and lan. Unless you have a server, I recommend that you get a small pc with dual nics.
-
The pc is running Windows Server 2016, sorry i should of mentioned that before, it also meets all the hardware requirements needed for pfsense apart from the dual nics which is why I've ordered another nic today :)
-
The pc is running Windows Server 2016, sorry i should of mentioned that before, it also meets all the hardware requirements needed for pfsense apart from the dual nics which is why I've ordered another nic today :)
Okay, that's another matter. I'll explain how I have my system set up and you can see if that makes sense for you.
My system has 3 nics, wan, lan and other. The wan and lan nics are externally connected to the bridged port on the modem and and a physical ethernet switch, respectively. Internally, they are connected to virtual switches. The lan switch is set to allow the management operating system to share the lan nic. The wan nic is also set to enable source mirroring so I can connect a virtual pc to the switch running wireshark.
With this configuration, I can have multiple pfsenses connected to the wan switch and I can even have a completely virtual lan and virtual clients. I can also have physical clients on the physical lan switch. I've been using this configuration for several years and it works well.
The "other" nic is connected to a lan port on the modem so I can access the modem GUI from the hyper-v server. (I bumped up the routing metric on this interface so no traffic will exit.)
Feel free to ask more questions if you have any.
-
The pc is running Windows Server 2016, sorry i should of mentioned that before, it also meets all the hardware requirements needed for pfsense apart from the dual nics which is why I've ordered another nic today :)
Okay, that's another matter. I'll explain how I have my system set up and you can see if that makes sense for you.
My system has 3 nics, wan, lan and other. The wan and lan nics are externally connected to the bridged port on the modem and and a physical ethernet switch, respectively. Internally, they are connected to virtual switches. The lan switch is set to allow the management operating system to share the lan nic. The wan nic is also set to enable source mirroring so I can connect a virtual pc to the switch running wireshark.
With this configuration, I can have multiple pfsenses connected to the wan switch and I can even have a completely virtual lan and virtual clients. I can also have physical clients on the physical lan switch. I've been using this configuration for several years and it works well.
The "other" nic is connected to a lan port on the modem so I can access the modem GUI from the hyper-v server. (I bumped up the routing metric on this interface so no traffic will exit.)
Feel free to ask more questions if you have any.
Thanks for the info, so from what you've said wan and lan nics can go to the ethernet ports on my router and i can still let the router handle dhcp and the wan connection? Or do i need to have a physical switch as well in order to do this? Obviously I'll have the wan and lan nics connected to the virtual switches running in hyper-v as well. New nic is arriving tomorrow so hopefully I'll be able to access the web configurator again at least which is what I'm struggling to do at the moment even with the existing nic i have which is set up with pfsense too :-\
-
The pc is running Windows Server 2016, sorry i should of mentioned that before, it also meets all the hardware requirements needed for pfsense apart from the dual nics which is why I've ordered another nic today :)
Okay, that's another matter. I'll explain how I have my system set up and you can see if that makes sense for you.
My system has 3 nics, wan, lan and other. The wan and lan nics are externally connected to the bridged port on the modem and and a physical ethernet switch, respectively. Internally, they are connected to virtual switches. The lan switch is set to allow the management operating system to share the lan nic. The wan nic is also set to enable source mirroring so I can connect a virtual pc to the switch running wireshark.
With this configuration, I can have multiple pfsenses connected to the wan switch and I can even have a completely virtual lan and virtual clients. I can also have physical clients on the physical lan switch. I've been using this configuration for several years and it works well.
The "other" nic is connected to a lan port on the modem so I can access the modem GUI from the hyper-v server. (I bumped up the routing metric on this interface so no traffic will exit.)
Feel free to ask more questions if you have any.
Thanks for the info, so from what you've said wan and lan nics can go to the ethernet ports on my router and i can still let the router handle dhcp and the wan connection? Or do i need to have a physical switch as well in order to do this? Obviously I'll have the wan and lan nics connected to the virtual switches running in hyper-v as well. New nic is arriving tomorrow so hopefully I'll be able to access the web configurator again at least which is what I'm struggling to do at the moment even with the existing nic i have which is set up with pfsense too :-\
I attached a picture. Maybe it helps. The AP, along with pcs and other devices are on the lan switch.
![Network 2.PNG](/public/imported_attachments/1/Network 2.PNG)
![Network 2.PNG_thumb](/public/imported_attachments/1/Network 2.PNG_thumb)