Hi BiPa Right now,- everything is deleted.  :) I tried at least 10 different setups, small variations and much, I had it running for a long time before the new install and upgrade to 2.4. No matter what I do, pfSense makes a round-robin on the webservers. I will set it up again and post the config, I just got the idea that the problem was in the software. Thanks for your answer  :)

That's normal, the setup for UEFI and such makes it look a bit unusual but it's all expected.

I had the same problem with a pfSense 2.3.4_1 to 2.4.0 upgrade on VMware ESXi 5.5 where the firewall would stop at the "db>" prompt afterward. I reverted back to the 2.3.4_1 snapshot taken just before the upgrade and tried upgrading to 2.3.5 instead. That worked (though I had to force power cycle the VM during the upgrade to get it to finish). I then took another snapshot at 2.3.5 and then upgraded directly to 2.4.1 and that worked also (no issues at all). I also noticed that from 2.3.4_1 only 2.4.0 was being offered as the "current" version to upgrade to (when 2.4.1 is actually the latest version). After upgrading to 2.3.5, version 2.4.1 (the actual latest current version) was being offered as the latest version. To summarize, for me stepping through 2.3.5 from 2.3.4_1 allowed me to get to 2.4.1 without making any file edits in FreeBSD. I also had 4 packages installed (AutoConfigBackup, ntopng, Open-VM-Tools, and openvpn-client-export) at the time of the upgrade and they also updated without issue. Regarding other attempts to upgrade other pfSense firewalls from 2.3.4_1 to 2.4.0: I had the same issue with a virtual firewall on ESXi 6.5 but bricked the firewall (was never able to get it to reboot and did not take a snapshot before the upgrade so had to install from scratch (it was a simple firewall so not a lot of work to start over with that one). I had no issues at all on an actual NetGate/pfSense hardware firewall I manage going from 2.3.4_1 to 2.4.0 and then on to 2.4.1. Update: I upgraded three more pfSense v2.3.4 (no "_1" or "p1") virtual machines on ESXi 6.5 tonight. Of the three, two correctly detected the latest stable version to be 2.4.1 and upgraded flawlessly. One detected 2.4.0 as the latest version instead of 2.4.1. I went into System-Update-Update Settings and changed from "Stable" to "Security/Errata only" and it correctly detected 2.3.5 as the latest release within the 2.3 track. I then switch the setting back to "Stable" and it then correctly detected 2.4.1 as the latest stable release. I then let it upgrade and it went flawlessly. It seems there is something inconsistent in 2.3.4 and 2.3.4_1 to properly detect the latest stable release to upgrade to. It also seems there are issues with 2.4.0 and VMware. v2.4.1 seems to work correctly and consistently within VMware.

same issue here, except  32bit/x86 full install on Virtual Machine and pc, instead of Alix.  the same fix worked. maybe this should be sticky?

I wonder if installing vanilla freebsd 11.1 would shed any light? I would also add that having it in a VM is very convenient because it presents a consistent hardware layer and allows easy rollbacks.

Thank you. Hope the backup/restore will work perfectly ;-) Alix2D13 is 32 bits only. I'will buy apu2c4 to replace it and install 2.4 then 2.5 …

Hi, I gave up on pfSense and decided to try OPNsense. It had exactly the same problem. That sent me back to basics, and I found that I had not enabled virtualisation (Intel VTX) in the BIOS of the KVM server. I knew it was required, and had though it was enabled, but it was not. With virtualisation enabled in the BIOS "pfctl -s all" shows a healthy set of filter rules, and the bogons error message in the log is gone. Problem solved. What led me somewhat astray was the fact that I had another FreeBSD 11.1 virtual machine running just fine on the same KVM server. Hope this helps for those who follow via Google… Cheers, Phil

Oké thanks for the update. Just fyi and anyone else running into that last error "undefined function install_package()" i have made a little fix for that: https://github.com/pfsense/pfsense/pull/3866

Hello Guyz, I am new in pfsense i was trying to install pfsense 2.3.5 from usb on dell optiplex 755 with 500gb hdd , 4 gb ram with  but i am facing AHCI time out cannot install… can you help me how to resolve this or this hardware is supported .

After Update to 2.4.1 Internal Server (IP) is blocked On what you were updating the pfSense firewall? (x86 32Bit hardware or software release or perhaps both?) From what entire version you were updating it to the version 2.4.1? From 2.2.6, or from 2.3.2 or from 2.4.0? What a kind of installation is it right now? USB pen drive install (NanoBSD) or a 32 Bit installation? Are VLANs are in usage there in front of the eMail server or the WAN port?

I am pretty sure this should be coded as a packet for pfSense and not naively installed on a pfSense firewall it self. Perhaps this is something to install on a smaller device that is collecting the information's from the pfSense firewall like PRTG with 100 free on a small Windows server or perhaps a RaspBerry PI 3.0 with Linux CACTI and MRTG would be nice matching to watch the entire pfSense stats and logs well. Have a look under the packet wishlist and post it there too, perhaps someone will code a packet for pfSense if many users will be considering. A better chance like here I think.

There has been a correction to the wiki page. The correct config file version number for 2.4.1-RELEASE is 17.3. 2.4.0-RELEASE is 17.0.

You need to (All under System > Routing): 1. Create a gateway on the LAN interface (em1) for 10.50.0.190. 2. Create static routes for 192.168.0.0 /16, 172.16.0.0 /12, and 10.0.0.0 /8 with that gateway as the destination. 3. If those routed subnets need to make connections into the em1 interface, the firewall rules there must allow those sources. No other way of creating static routes is correct or supported and if you are playing around manually adding routes in the shell it is not really any surprise you had trouble when you upgraded. Nothing here changed between 2.3.4 and 2.4.X. Gateways and static routes all upgrade just fine.

@kpa: On pfSense the file you want to edit is /boot/loader.conf.local and you probably need to create it yourself because it doesn't exist by default on pfSense. The /boot/loader.conf file is a reserved file and gets overwritten every time a new base system update is performed. Note that this is different compared to a stock FreeBSD where /boot/loader.conf is free for all to edit. Thanks for that clarification, I'll make sure to edit that on mine instead.  Saved me some headaches later there :)

No, two threads are not enough. Let's find a third one to hijack! Pardon my sarcasm.

I was going to respond with a link to the same thread - I have not had a chance to re-install and setup.  Pretty frustrating that a minor release brought down the whole thing. I just switched to PFSense a few months ago - Release notes or not, I would not have expected, in 30 years in the IT business, that a point release would be able to bring down my network because of an internal device naming convention, but then again, I did see SMS 1.2 and OS/2 do some pretty nasty things on upgrade.  So, note to self - 'stable' in the pfsense world means it has passed some testing, but ALWAYS read the forums first, point release or not.

yes.  works fine.

Hi, Update from 2.4 to 2.4.1 and I have same issue as user who started this topic.  

Thank you for the useful info. I believe I have now a device ready for a hot swap. What I've done was: downloaded pfSense-CE-2.3.4-RELEASE-4g-i386-nanobsd.img from https://atxfiles.pfsense.org/mirror/downloads/old/ written it to 4GB CF card using  http://sourceforge.net/projects/win32diskimager/ exported config from the old remote 2.0.1 device via web GUI renamed the file to config.xml and copied via USB stick to /cf/conf/ on the new 2.3.4 device restarted 2.3.4 and it appears to successfully embed the new config (viewed from serial console). That's probably as much as I can do before making a trip to the DC and swapping devices. Could somebody take a quick look at the boot log and point out any potential problems (if any)? I have replaced real DNS names and IP/MAC addresses with dummy ones but it shouldn't alter the original concept. Thanks Adam config-import-log.txt