Worked perfectly! Thank you!

Thank you Steve for the insight. That was very helpful.

@kiokoman thanks!

That's a Hyper-V issue, not pfSense. Probably a boot option like "Secure Boot" you can disable to get past it.

@Nullity, I was facing the same problem, " CAM status: Command timeout" and your answer worked for me on pfsense 2.4.4 installation using a pendrive: I've add "set hw.ata.ata_dma=0" on boot options and install proceeded with no errors. Once pfsense installed, it was needed to edit the /boot/loader.conf file and add the same option so that persist it on next boot. Thanks.

The switch issue appears to be a general problem on 2.5.0 right now, at least on the 3100.

@robina80 said in Installing mSATA on APU board: i have succesfully done it downloaded and put the image on my usb stick using "win32 disk imager" inserted it in free usb port connected serial cable to laptop, opened up putty and changed baud rate to "115200" to see the boot menu and boot of the usb closed/opened putty again and changed the baud rate to "9600" so i can install and follow the on screen instructions once done i changed my boot order so the first option was my mSATA once i could log back in the webgui i restored my settings so it was like how i had it before Hi ! I faced up to a BIG trouble while upgrading to the latest version of pfSense (2.4.4-RELEASE (Patch 3) ) : unable to boot, something to do with CPU microcode update ? # service microcode_update start If the CPU requires a microcode update, a console message such as the following will appear: Updating CPU Microcode... /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done. /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done. Done. >>> Setting vital flag on pfSense... done. External config loader 1.0 is now starting... ada0s1 ada0s1a ada0s1b Launching the init system...Updating CPU Microcode... Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x800e29000 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff81189dde stack pointer = 0x28:0xfffffe0035f2a940 frame pointer = 0x28:0xfffffe0035f2a940 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 608 (logger) I proceeded like robina80 explained, booting from USB with "pfSense-CE-memstick-serial-2.4.4-RELEASE-p3-amd64" version, USB keyboard attached, Serial port to 115200 ==> Everything went back, pfSense is now able to boot ;-)

Hello. I have re-installed the squidguard package and re-booted the firewall. Now I can see squidguard on the services menu. And I have not lost the previous configuration for the service. Next step: play with the ssl url filtering. Thanks for your help.

basically my routers are aging and instead of going with expensive home network crap i want to build my own network solution out of my old workstation why because find me a router with a 3.2GHz core 2 quad 8GB ram and i was originally goig to use x86 ddwrt but then i found pfsense and saw how much i could improve my network security and how i could seperate my server and home network

I know this topic is quite old, but did anyone resolve this issue? I am running into the same thing. [2.4.4-RELEASE][root@att.com]/var/run: ls -l total 144 drwxrwxr-x 2 root operator 512 Sep 29 03:08 .snap srw-rw-rw- 1 root wheel 0 Sep 29 03:08 check_reload_status -rw------- 1 root wheel 3 Sep 29 03:08 cron.pid -rw------- 1 root wheel 3 Sep 29 03:08 devd.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:08 devd.pipe srw-rw-rw- 1 root wheel 0 Sep 29 03:08 devd.seqpacket.pipe lrwxr-xr-x 1 root wheel 19 Sep 29 03:08 dmesg.boot -> /var/log/dmesg.boot -rw-r--r-- 1 root wheel 5 Sep 29 03:09 dpinger_WAN2GWv6~2001:1890:c03:960::11e5:95e2~2001:1890:0c03:0960:0000:0000:eee5:95e2.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:09 dpinger_WAN2GWv6~2001:1890:c03:960::11e5:95e2~2001:1890:0c03:0960:0000:0000:eee5:95e2.sock -rw-r--r-- 1 root wheel 5 Sep 29 03:09 dpinger_WAN2GW~206.121.142.210~206.121.142.209.pid srw-rw-rw- 1 root wheel 0 Sep 29 03:09 dpinger_WAN2GW~206.121.142.210~206.121.142.209.sock -rw-r--r-- 1 root wheel 6 Sep 29 03:09 expire_accounts.pid -rw-r--r-- 1 root wheel 25478 Nov 5 14:18 filter_reload_status -rw-r--r-- 1 root wheel 6 Sep 29 03:09 filterdns.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 filterlog.pid -rw-r--r-- 1 root wheel 6 Nov 5 14:20 haproxy.pid -r--r--r-- 1 root wheel 230 Sep 29 03:13 ld-elf.so.hints -r--r--r-- 1 root wheel 129 Sep 29 03:13 ld-elf32.so.hints srw-rw-rw- 1 root wheel 0 Sep 29 03:09 log srw------- 1 root wheel 0 Sep 29 03:09 logpriv -rw-r--r-- 1 root wheel 6 Sep 29 03:09 nginx-webConfigurator.pid -rw-r--r-- 1 root wheel 5 Sep 29 03:09 ntpd.pid -rw-r--r-- 1 root wheel 6 Sep 29 04:19 openvpn_server1.pid -rw-r--r-- 1 root wheel 5 Oct 14 11:17 pfSense-upgrade-GUI.pid -rw------- 1 root wheel 25 Nov 11 11:46 pfSense_version -rw-r--r-- 1 root wheel 1 Nov 11 11:46 pfSense_version.rc -rw-r--r-- 1 root wheel 3 Sep 29 03:08 php-fpm.pid srw------- 1 root wheel 0 Sep 29 03:08 php-fpm.socket -rw-r--r-- 1 root wheel 6 Sep 29 03:09 ping_hosts.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 radvd.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:08 sshd.pid drwx--x--x 3 root wheel 512 Oct 14 11:17 sudo -rw------- 1 root wheel 5 Sep 29 03:09 syslog.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 unbound.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 update_alias_url_data.pid -rw-r--r-- 1 root wheel 6 Sep 29 03:09 updaterrd.sh.pid -rw-r--r-- 1 root wheel 0 Sep 29 03:08 utmp -rw-r--r-- 1 root wheel 394 Nov 11 11:47 utx.active -rw-r--r-- 1 root wheel 6 Sep 29 03:09 xinetd.pid drwxr-xr-x 2 zabbix zabbix 512 Oct 14 11:17 zabbix-agent I am also having an issue with the /var/run folder getting filled up due to Zabbix. I have to uninstall Zabbix from pfSense and the file goes from being really small to about 3 megs in a week. [2.4.4-RELEASE][root@att.com]/var/run: cd sudo [2.4.4-RELEASE][root@att.com]/var/run/sudo: ls -l total 4 drwx------ 2 root wheel 512 Oct 14 11:17 ts [2.4.4-RELEASE][root@att.com]/var/run/sudo: cd ts [2.4.4-RELEASE][root@att.com]/var/run/sudo/ts: ls -l total 3168 -rw------- 1 root wheel 3211264 Nov 11 11:53 zabbix [2.4.4-RELEASE][root@att.com]/var/run/sudo/ts: I was not having this issue until I updated pfSense to 2.4.4 release p3 about 2 months ago. Thank you for any help you can provide.

@stephenw10 ntopng is the only thing's broken i think

Bad drive maybe? Can you drop to the command line and check dmesg for errors?

the big mystery part is that the wan is always online and only the virtual lan go off.

Solved! I reinstalled and all work!

Hi, The subject is known. Bad WAN, bad files system, broken DNS, etc. Use a the magic keyword "repo-pfSense-core.sqlite" and put it in here : [image: 1572869187639-c7ac8ca7-70f6-415c-bf73-61d4c9791943-image.png]

@bjohe Yes, since I have setup my WAN as default gateway I didn't have any internet dropout. In your case did you consider a hardware failure? Trying to debug my issue I have bought another (actually 2 other relatively cheap used LAN cards from ebay) and added to my setup trying to exclude the lan card failure, but in my case it was not the card.

Oh cool thank I was hoping that would work but wasn't sure. I remember something about when I tried to upgrade the current device I had to remove all packages or something. I never got it working well on 2.4 it was just too slow once it was upgrade so ive built a low power pc to replace it. Yeah all the network cards are different and there are more now, shouldnt be a big issue from what you've said. Many thanks will give it a go as soon as I get chance. Regards Rob

Indeed! Searching this site with the CVE identifier (CVE-2019-11043), I found this: https://forum.netgate.com/topic/147590/cve-2019-11043/5 I just had the feeling that the updates to pfSense are not frequent enough (I have it installed a couple of months now and I got no updates to the main software yet, only some packages). So, I was wondering if I was missing some critical maintenance action... I guess I can chill now... Thanks.

As in Rico above link, Bios and system time check this first please