Hyper-v WAN issue
-
Hello,
My problem just recently started originating since I upgraded my hyper-v pfsense to the latest 2.0.3
For some reason, nothing but issues with the WAN side. As it sits, if I reboot the virtual machine, WAN goes back to DHCP and picks up a local address and shows this in the console. However the web portal still shows the WAN to be still on the static. Switching the WAN address in console, turning interface de0 down the back up after seems to fix it. Sometimes I may need to go into routing and manually add the gateway IP under the alternative to show gateway is online. This has to be done everytime I reboot the machine and is turning into a huge pain. Once I do this everything runs fine, however a simple reboot can turn into a nightmare.
All of DHCP/DNS are done from a 2008 R2 DC which is virtualized as well.. That machine is plugged into a 24 port unmanaged switch, along with my non virtualized pfsense and also my modem. The other pfsense is my main and runs on an Alix board with 2.0.3 and no issues.
-
Bump…anyone?
-
I have found that hyperv and pfsense dont mix well together.
Although having said that, here's a few tips i use with linux boxes in hyperv:
- make sure you have the modules for hyperv installed.
- make sure that you have the network cards on static mac addresses
I find that sometime my centos boxes network cards just stop working and nothing but a reboot sorts it out.
I highly suggest running pfsense on just about any other hypervisor than hyperv.
-
2.1RC seems to working fine. No issues yet.
But its always had:
- make sure you have the modules for hyperv installed.
- make sure that you have the network cards on static mac addresses