Hi, I have no problem running pfsense on ovirt i think you should either create a at least two vNIC on ovirt and attach it to the pfsense vm for WAN and LAN or PCI-passthrough a NIC to it

There is a new(older) recovery image in the portal, which seems to be working…. Hurrah!

Ok good to know. Will keep a lookout for which variant you will keep.

@Gertjan: Hi, Just an idea : setup the logger ( Status System Logs Settings) to an external log server so you can see up until which point all your interfaces are going down - or the unit becomes brain-dead. Be sure that reflashing to the version before doesn't give you the same situation. It seems this is a good idea to troubleshoot the problem.  I just don't know how to setup an external log server.  At the moment I will be setting up my network like this just to simulate it the problem keeps on coming on PC2 as well as the connected wireless device at UNIFI AP. MODEM–---->ASUS RT-N56(192.168.1.1)------>SWITCH1-------->(192.168.1.2)PFSENSE(10.10.10.1)-------->SWITCH2----->PC2                                                                             |                                                                                            |                                                                             |--------->PC1                                                                          |----->UNIFI AP

@stevehaley: I keep seeing references to posts that claim that it is possible to configure pfsense to establish the gre tunnel with the hitron in modem mode in order to login for the stAtic ip on virgin. Has anyone managed this? I cant even get pfsense to get a dynamic address when the existing smarthub 2 is in modem mode and have to spoof the mac address. The Hitron and Smarthub are two completely different devices, aren't they?

Glad its not just me. I even resorted to "pkg-static upgrade -f" just to make sure nothing had become corrupted, it took about 4 hours to download and reinstall 10MiB. It definitely seems to be something very wrong in the package manager itself.  Its not working at all from the UI but that is probably timeouts due to how very slow its running. Downloading something via curl on the command line does my line speed.  Downloading from the mirror site directly works fine.  All other functionality of pfSense is absolutely fine.

hhajj: You mention that after few minutes, connection to web configurator is lost. Did you get the 502 bad gateway error? If so you are not alone  :-[ Have a look here https://redmine.pfsense.org/issues/6406 Looks like the bug is one year old and that progess is 0%.

I followed this guide: https://www.netgate.com/docs/sg-1000/faq.html#how-do-i-restore-the-firewall-os-firmware And flashed the image to USB using this command: https://www.netgate.com/docs/reference/create-flash-media.html#linux-freebsd-mac-os-x Then when I had the OTG cable plugged in, with the USB connected, it gave a re-flash option from the console on first boot. Hope that helps.

Not yet.

I logged on to my pfSense today and was pretty horrified to see a 502 error page. I didn't want to reboot until I understood the cause. I did have the OpenVPN Widget and IPSec VPN Widget running on the homepage of pfSense. I also changed my firewall logs to show 20 results, show FAIL & REJECT, and refresh every 1 second. Perhaps this was a bit too aggressive. My OpenVPN clients couldn't connect via OpenVPN but IPSec VPN was able to still connect. As advised earlier, restarting PHP-FPM using the numerical menu options in the pfSense console allowed the OpenVPN tunnels to connect again, and removed the 502 error. Hope this helps.

What does npcap loopback adapters have to do with anything? Why do you have npcap even installed?  Are you running wireshark?  That has zero to do with your machine clearly got an 192.168.1.101 address from a dhcp server.. IPv4 Address. . . . . . . . . . . : 192.168.1.104(Preferred)   Subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Sunday, May 14, 2017 5:10:03 PM   Lease Expires . . . . . . . . . . : Sunday, May 14, 2017 7:10:03 PM   Default Gateway . . . . . . . . . : 192.168.1.1   DHCP Server . . . . . . . . . . . : 192.168.1.1

@Chti: Last night I decided to upgrade my SG-4860 from 2.3.3.1 to 2.3.4. So I hooked up the console, and the device boots up for a few seconds but then remains indefinitely at a "Boot: F1" line. Honestly, I'd just call them Monday.  There have been a few similar posts in the official hardware forum and they've really been extremely helpful to people who have had problems with updates of both BIOS and pfSense itself.  You might want to check a few of those posts too, maybe there is something there. Rick

I don't have a Dell server , but had the same errors on an AMD LX800 Geode. I ended up using the CD instal w. an USB attached DVD drive. Remember to set the set kern.cam.boot_delay="10000" My post https://forum.pfsense.org/index.php?topic=127036.msg701568#msg701568 /Bingo

It seems there is a problem with pfsense kernel upgrade on nanobsd … for some reason it remains locked and cannot be upgraded using GUI or pfSense-upgrade ... The solution is to do regular upgrade and than go to shell and execute: pkg unlock pfSense-kernel-pfSense pkg upgrade pfSense-kernel-pfSense pkg lock pfSense-kernel-pfSense reboot

I did. I used an usb to install Pfsense and the error is from that installation using pfSense-CE-memstick-2.3.4-RELEASE-amd64.img. @johnpoz: At a loss to what your trying to do?  The memstick images are meant to be written to a usb stick.. And then booted from that stick.. https://doc.pfsense.org/index.php/Writing_Disk_Images