@Arnaud.D: Thank you for your answer. I think we will have to do so, but I hoped that I could have do this on a easier way. what i've suggested is the easiest way

lol I guess its been a while since I have made a liveCD myself. I didn't even realize they discontinued it. My overall goal was to run from "read-only" media. I might be better off using a linux distro to achieve my goal.

@haleakalas: Try to add the following line in /boot/loader.conf.local as well as /boot/device.hints hint.hpet.0.clock=0 (Having it in one of the files should suffice but I can't remember which, as I did this once some time ago. In any event it won't harm your system if you have it in both places) Alternatively you might want to go into your NUC's BIOS and check the ACPI section. If there is something called CSM or Compatibility Support Mode or Legacy Compatibility mode which is ON try to turn it off and reboot. Sorry to bring up a relatively old post but I just wanted to thank you for this.  I've never had this issue until I tried to upgrade to 2.4 this morning.  Adding this line to /boot/loader.conf.local got me back up and running.  Thanks again!

@kyualex: I'm so sorry! I took the password from config export of the previous firewall. I should have noticed the "=" sign at the end of pawwsord to notice it has been encrypted  :-[ :-[ [/quote] Not encrypted, base64 encoded. You can use a base64 decoder to get the real password.

Hi, Use the GUI (Diagnostics menu) and the console access to check if your pfSense has an Internet connection. Btw : I voted "1" - or should I vote for the other "1" ? Your vote proposal and question are not clear at all.

Yes you can. The issue with most USB connected GPS devices though is that they don't provide the PPS signal. And yes USB connected GPS as a time source is bad….very bad! But also fun.  ;) Steve

It is possible to override parts of the ACPI tables to by-pass things like this. https://www.freebsd.org/cgi/man.cgi?query=acpi&apropos=0&sektion=0&manpath=FreeBSD+11.1-RELEASE+and+Ports&arch=default&format=html But that should not be required. You might enable acpi debugging info, that might give you more idea what's happening. hw.acpi.verbose=1 The fact you are hitting this and even others running the same hardware are not implies either you have a faulty board or you have added something faulty to it or you have a different BIOS version. Steve

The haproxy config won't be removed when you uninstall. That all stays in place. Once you reinstall haproxy the settings will all still be there.

The config upgrade code steps nicely through each upgrade step 1 at a time, and each step deals separately, in time order, with config format/data changes required for a particular new feature/fix. I reviewed it all "some time ago" for any bits that might go wrong, and it is all good as far is I could see. You can restore an old config from any old pfSense version (and even an old m0n0wall config) and the system will reboot and apply all the needed upgrade steps. So choose whichever path you like - upgrade the existing 32-bit system to 2.3.5 then save the config, install a 64-bit system and restore the config; or save the existing "old" config, install a 64-bit system and restore that old config either will work equally well.

Thanks bfeitell! I recently updated my pfsense install to a UEFI install to take advantage of the real estate of my 3840x2160 resolution monitor via the console and I had some screen tearing at the bottom which obfuscated the active command prompt. I've been searching for a solution for close to a week and had tried everything from attempting to load vesa.ko and i915kms.ko (for my Intel HD graphics), to trying to get the vidcontrol command to work, to trying to edit /boot/loader.conf with kern.vty=vt,  kern.vt.fb.default_mode="<x>x<y>", etc. This is the only solution that actually worked for me! Edit: I stand corrected. I was able to change the resolution by interrupting the boot process, but I can't get the setting to load automatically with the /boot/loader.rc.local file.</y></x>

Thank you!  I have the same problem.  Somebody please fix this.  Who manages the package?

The router in front of pfSense has to have a NAT rule to pass along the incoming VPN connection. If you use the VPN server from pfSEnse, no. Can't tell. I do not have a clear view your network. But, as always, a VPN - and surround firewall - with a good setup doesn't "leak". Let's Begin! 1.) Start by downloading one of these certificates to your computer: …... This is a joke or what https://www.privateinternetaccess.com/forum/discussion/29231/tutorial-setup-pia-on-pfsense-2-4-2 ?

Looks like I may have found the issue. Under System > Advanced > Miscellaneous > RAM Disk Settings - I unchecked the "Use memory filesystem for /tmp and /var" and the issue seems to have gone away, with the CPU idling around 17% - but only time will tell.

More like every week ;)

Hi, thanks for your advice. Sorry for the late reply, I was on holidays for a week. When I came back and checked the update status of the box it offered me to upgrade to the 2.4.2_1. And no, as I was on holidays I really did not change anything! As soon as I clicked on the "upgrade now" it still does not offer to upgrade. This is the dashboard:``` 2.4.2-RELEASE (amd64) built on Mon Nov 20 08:12:56 CST 2017 FreeBSD 11.1-RELEASE-p4 Version 2.4.2_1 is available. Version information updated at Sun Feb 11 19:30:25 CET 2018 In System -> System Update (After clicking on the blue cloud to download) it says:``` 2.4.2 Latest Base System 2.4.2 Status Up to date. So obviously there is an issue- one page shows I can upgrade while the next says it is up-to-date. Unfortunately I cannot use the option to start the upgrade through ssh as I am remotely (and ssh connection will brake when updating remotely). Does someone know what the URL for the upgrade check is? Perhaps there is a DNS glitch or proxy issue. Thanks for ideas! /KNEBB

Well I answered my own question.  When I installed and booted it told me my VLAN parent interfaces no longer existed and I had to fix.  So I set all the interfaces and hit save and seemingly nothing happened.  A freeze up.  I scratched my head and tried again and then again and then I actually looked at the VGA monitor instead of the webconfigurator and saw the word "reboot". It saved the config and then rebooted…........and came back alive with a new IP address.  D'oh.  I did it right the first time. I'll yank the SG-2220 tomorrow and install the new device.  Should be plug and play at this point.

i just uploaded the next crash dump from the same IP address. I thought I caught the problem: After removing all traffic limiter things seemed to get better. But after connecting our second WAN and our LTE connection reboot failed. Next boot was successfull and brought the mentioned crash dump.