Guys, Solved this for myself. Even though dashboard said I was up to date, I wasn't. Running console update [option 13] did a kernel update and two reboots. After that, I was back in business. Hope that helps someone … Chip

These instructions solved the problem for me https://forum.pfsense.org/index.php?topic=138564.msg757525#msg757525

It's very likely that pfSense disables the 32-bit emulation layer and runs only native 64-bit binaries from version 2.4 onwards. The 32-bit emulation layer is a kernel option that needs to be on at compilation time, there is no workaround if the kernel option is not turned on.

I recommend replacing that disk with a new one.  My best guess is what's happening is that during the rules download (when the Snort GUI process is writing the downloaded blocks to disk in a temporary directory in /tmp), the disk write is randomly failing.  When that happens, the OS is probably stuck trying repeatedly to make the write of the failing block.  That would be why the process would seem to "freeze" at times when you are watching it (like during the package install when it downloads the rules).  With disk failures, it is not uncommon for the low-level I/O driver to repeatedly attempt the write operation.  It will eventually give up, but sometimes it takes a while depending on the particular operating system. The fact you see whole parts of your configuration disappear lends further credence to bad hardware (in this case it appears to be the new SSD).  I know in the past I've unfortunately purchased new conventional hard disks that were dead out of the box (DOA).  The same thing can happen with an SSD.  In your case it appears as more "flakey" that just simply DOA. Bill

Unlocked the topic. I'm not sure who locked it, it was probably done in mistake. Thanks!

Hi, When you (re) install, pfSense is clean - and then you set it up with your local settings. This could be as simple as : have it read a copy of your earlier config.xml file. If this config file contains info about packages that were present at that time when the copy was made, pfSense will re-install the packages in the background. If the related settings are 'wrong', well, then many things can happen. Just have a look at the config.xml file - it's very readable by humans) and use the magic key shortcut Ctrl-F and look for "snort" and "suricate". If these are present, I advise you to re install pfSense again, NOT importing your config.xml, but use it as a guideline to redo your setup like WAN access, networks, etc. You'll be done in several minutes, and winding up with a clean box.

@hsj18: OK guys, need some help because the wife is mad I keep taking the wireless down lol. Normally, you test drive first - hook up pfsense to your your device (router) that realizes your connection, activating DHCP client on WAN so it gets an IP like any other device, hook up your PC on the LAN side and play with it. Then add a AP on the LAN segment, connect PC using Wifi to AP, test again. When all is ok, you switch you home network to the new setup. For every user this instant change will be completely transparent. @hsj18: Question 1. Do I need a switch between the AP and the WAN port? A schema, please ? But remember : did you ever saw such a setup like this on the net ? APs, in this case, are just devices on your LAN that transport wireless data to cabled data. They are transparent. An AP should not work in router mode - it should have an (static) IP on LAN, gateway should be the IP used by pfSense (192.168.1.1), as does it's DNS. Done. @hsj18: Question 2. After initial setup, should I have to change DNS? This can be answered when you made up the inventory will all kind of requirements before you start. Like, what is the type of connection you used before ? What is special ? What is classic ? What did you use before (OpenDNS, or do you like to sell all your DNS traffic to Google ? etc.) In most cases, people should stick with the "keep it simple" rule. This means that pfSense need's be be installed, and you never touch DNS settings. It works perfectly out of the box.

Same question here.  I have a low-end laptop that has a bad SATA channel (so the HDD and DVD don't work).  I've run Linux and CloudReady from the USB fine, so I know those ports work.  I'd put a USB flash in one port and a USB ethernet in the other, until I can pick up some proper hardware.

Rebooting the SG-3100 via console fixed the issue after resetting.  The reboot did not fix the error initially, after I had changed the IP via GUI.

D'oh. I had a GEOM mirror that I deactivated prior to upgrade for emergency fallback. Turns out everything is fine; after syncing the right kernel was booted from the primary ssd. Oooookay. Thanks :) -Chris.

https://forum.pfsense.org/index.php?topic=142267.0 https://forum.pfsense.org/index.php?topic=142598.0 In short: I beleive my issues are related to the APU2 BIOS. I've rolled back all but one unit to BIOS V4.0.7. So far, no issues with those routers for the last few days.

Not really.

This is called "router on a stick", and you will need to utilize VLANs and a switch capable of tagging (aka a smart / web / managed switch). Lots of examples online if you search for that term for what you want to do :)

Hello I too am attempting to boot the iso using loopback, but am unsure of the grub parameters. Has anyone had any success at this? Thanks /joe

Thank you OP, this was a nice learning experience. Well worse case scenario, I only had to re-install from media, then restore the config xml file. as I've done in previous failed major version upgrade. but is good to learn how to re-cover from a bad upgrade. Almost every major version upgrade like this 2.3.4 to 2.4, or 2.x to 2.3, and all previous major number changes, seems to have problem upgrading properly.

"Is there a safe way to upgrade ntopng to 3.2? " wait til they update the actual pfsense package…

Hi, thx for reply. All disks are straight out of the box. All brand new ones. It's only the installation that fails in one point. Now I have used my "old" APU1 unit to install pfSense and then moved disk to new APU3 unit. Then disks works just fine. Thats why I wonder if there is an issue with installer or need to tune delays for SD/msata???