Get a true AP, or use whatever old wifi router you have laying around as an AP to connect wifi to your lan network.

Roger that!

Thanks, guys.

I know the vlan labels changed but would that prevent them from pinging out?  I can't ping any ip address via that interface and I can't ping the interface IP from my desk.

@Derelict:

You have still not provided any console output from the VM host.

The console only shows the message about the admin logging in from a remote IP address. I have mitigated the issue by using physical hardware instead of a VM. When installing PFsense 2.4.1 to dedicated hardware the restore works (3 attempts out of 3 succeeded). When restoring to a VM (ESX 6.5 U1) the restore attempts (0 out of 6) are successful. Thanks!

The intel datasheet says 64-bit is supported. Where is the problem?

Go with version 2.3.5 it is maintained for ~12 month as I am informed right. And then you could change if you want
to a newer hardware platform, but you can also try out to disable the graphic unit inside of the mainboard and then
try installing the serial only version and not the VGA version. Could be running nice, but then a serial console cable
or USB to serial adapter will be a nice to have thing if you must connect through it.

Ok, you are right, it's MBR. I had installed it twice and the first go-around I had chosen GPT. I thought I had the second time too but I guess not.

Tried it again and it worked.  This time around, I switched to and from the Security and Stable lines.  Plus, I went back to the Dashboard between swaps.  I don't know which of the two made things different.  But, thanks all around.

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 .