PfSense 2.3.4 on Hyper-V Looses WAN connectivity after TWO hours
I've been running pfSense for a number of years on a stand-alone machine without incident.
I recently bought another computer with the intention of running pfSense under MS Server 2012 Hyper-V. I purchased a separate Intel Dual port Gig network card for the the pfSense VM. The setup is complete and functioning well (the VM system was uploaded from the export of the backup of the running Stand-Alone pfSense).
However, as mentioned in the subject every two hours I am forced to reboot the VM and (at times) acquire a new WAN IP. I have been playing with all the settings on the VM network cards without success. I've been systematically trying to eliminate and change network settings for a week to no avail. I was wondering if anyone here has had this same experience and possibly found a resolution.
Thanks for any advice.
could be the drivers, or it does not like having a dhcp in the vm
I'm running pfsense 2.3.4 and 2.4 beta on hyper-v 2012r2 with no problems at all. The WAN nic is intel i350-t2 and the LAN nic is on the motherboard. Both nics are connected to virtual switches and both pfsenses are connected to the virtual switches. (I have one physical LAN and one virtual LAN.) You probably have issues with drivers or other settings.
Update – I decided to start from scratch without importing the entire backup from the working standalone server.
Instead, I created a new VM from the current 2.3.4 and established a working (albeit sparse installation). From there I restored individual sections of the backup, each time rebooting to assure there was not an error encountered in the restore of the individual section. As it turns out, all went well and all the sections/modules are now installed again and working flawlessly.
With the above, the only thing that I can think of is that the complete restore process has some issues. Perhaps someone can help with debugging the complete restore process..
Anyway, thanks for the help.