Given that pfSense is a security product, keeping it up-to-date is critical to ensure that known security issues are addressed regularly. You don't have to jump right on every new release the moment it's out, but you should be getting things updated regularly. There is more general advice in the upgrade guide to help ensure things go smoothly.

The default speed on the installer image and after is 115200, but you might have 9600 stored in your config.xml. Check under System > Advanced, Admin Access tab, at the bottom in the console section. As for the speed in the APU BIOS, that should always have been 115200 as well, especially if you bought it from Netgate. To change that you'd have to go into the APU BIOS, directions for entering that should be printed at the start of the boot process.

@Cool_Corona hi! Another Dane here ;-) Usually when I test up against 'Fiberby ApS' in speedtest.net I get several hundred Mbps. I can see (from the page of the result ID of your screenshot) that we use the same provider (Nianet and I guess now it must be GlobalConnect for both of us). But of course we both might have some intermediary ISP in between (I have at least). Please could I ask you to test up against 'Fiberby ApS' (and maybe rerun your original test again)? But only of course if you are currently running pfSense 2.4.5-p1 as I understand if you might needed to roll back to get full speed or do not have time for more tests atm. I haven't updated yet to 2.4.5-p1 due to some preparations I have to make.

@revengineer Ahh, never did see that thread. Well I'm glad it's a known issue and I hope it gets fixed. Thanks for pointing that out and thanks for your help

db:0:kdb.enter.default> bt Tracing pid 12 tid 100266 td 0xfffff8000d85e620 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe0c580f6740 vpanic() at vpanic+0x19b/frame 0xfffffe0c580f67a0 panic() at panic+0x43/frame 0xfffffe0c580f6800 trap_pfault() at trap_pfault/frame 0xfffffe0c580f6850 trap_pfault() at trap_pfault+0x49/frame 0xfffffe0c580f68b0 trap() at trap+0x29d/frame 0xfffffe0c580f69c0 calltrap() at calltrap+0x8/frame 0xfffffe0c580f69c0 --- trap 0xc, rip = 0xffffffff8051fdd0, rsp = 0xfffffe0c580f6a90, rbp = 0xfffffe0c580f6b20 --- bce_intr() at bce_intr+0x500/frame 0xfffffe0c580f6b20 intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe0c580f6b60 ithread_loop() at ithread_loop+0xe7/frame 0xfffffe0c580f6bb0 fork_exit() at fork_exit+0x83/frame 0xfffffe0c580f6bf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0c580f6bf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- <6>bce1: promiscuous mode enabled bce2: Gigabit link up! Fatal trap 12: page fault while in kernel mode cpuid = 12; apic id = 20 fault virtual address = 0x10 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8051fcf0 stack pointer = 0x28:0xfffffe0c582fba90 frame pointer = 0x28:0xfffffe0c582fbb20 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 = 12 (irq258: bce1) trap number = 12 panic: page fault cpuid = 12 KDB: enter: panic Unfortunately there isn't much in the backtrace that would point to a specific cause, except it's crashing in the bce driver, apparently while processing an interrupt. Could be a driver issue, could be hardware.

@mauzilla said in can't upgrade from 2.4.3 to 2.4.5 with error message "Update origin security/php56-mcrypt -> ... failed": Were you ever able to resolve this? I am hoping someone can still give an update on how to get this resolved? I am worried that if we restart the firewall No luck so far, I haven't tried again since I saw people have issues on 2.4.5, I'll probably wait again until it's stable, btw my firewall reboot just fine, I'm running pfSense under Hyper-V so if anything goes wrong, I can restore the checkpoint.

reboot and run fsck https://docs.netgate.com/pfsense/en/latest/hardware/troubleshooting-disk-check-errors-fsck.html option 5 and F ffrom the menu

Once again the pfSense GUI Packet Manager got stuck after the most recent pfSense upgrade 2.4.5_1. Yet again it was pkg-static process which was stuck. Executed: killall pkg-static pkg-static upgrade -f Saved the day.

@bradbunch37 said in New pfSense User: Hello, The key is to avoid dual-NAT (if your ISPallows it): F.E.: https://forums.att.com/conversations/att-internet-features/how-do-i-configure-att-bgw210-in-bridge-mode/5defca9bbad5f2f606709d08 Orbi Wifi 6 AC4200 theme (use in AP mode): F.E.: https://www.youtube.com/watch?v=3YwkjTXrlsA build or buy a pfSense box and use this as a router + firewall (https://www.pfsense.org/products/) so,: ISP modem (BGW210-700 in bridge mode) + pfSense box + VLAN capable switch (even this is NetGear GS108) + WiFi AP (Orbi Wifi 6 AC4200) segment your network into VLANs +++++++ if you have separate ONT + ISP router / modem devices from the service provider, in most cases they really can't be separated, but bridge mode works well in many cases, if you ask your provider and system allows (this is a case of installation topology), you can leave your ISP router / modem and go directly to ONT eth. port for public IP

"I know nothing!" about the specific issue, but instead of fixing something by manually patching the interfaces.inc file I would suggest that you add a ticket on https://redmine.pfsense.org/projects/pfsense/roadmap as to describe the reason for a fix / patch with a detail about how it used to work when you patched the file. (You will have to login or create a pfSense redmine account on that site.) Also it would probably be a good idea to link this forum thread to the ticket (and vice-versa). It will save you from the trouble in the future as updates are released. Have a good day. :-)

hi, ive upgraded to 2.4.5-p1 without issues. I then reinstalled the box from scratch with that release. just had issues with auto install of avahi and pfblockerng packages. the rest seems to work normaly.

Tried it a third time and this time didn't get the pesky warning message about packages not available for the version. It went directly to installing the packages. YAY! But it still hangs on darkstat and pfBlockerNG-devel. I can kill those processes and go into Backup/Restore to reinstall all packages and it goes though and reinstalls everything in under 3 minutes. Any way to figure out why it is stopping installing those packages?

@teamits I did that already for two days. That's why I posted first email. Googling for boot hangs was getting me nowhere. I'll figure out howto put debugging statements in and figure out why it stops. Now I know it's the menu.4th menu.rc script that does all the menu including the timeout. It's just a bunch of loader script commands. https://www.freebsd.org/cgi/man.cgi?loader(8)

@Gertjan said in Idea for quicker CVE patching: json-c-0.13.1_1 is vulnerable: json-c -- integer overflow and out-of-bounds write via a large JSON file CVE: CVE-2020-12762 This one made it : https://docs.netgate.com/pfsense/en/latest/releases/2-4-5-p1-new-features-and-changes.html

See also https://forum.netgate.com/topic/142004/dhcp-config-is-apparently-not-updated-in-a-safe-fashion

@bigdaddycainer Yes i agree ,regression is the answer,unfortunately and painfully,hope i kept the old gz or iso as pfsense arent in the habit ( like they previosuly did) of visually indexing the links to each version,like they previously did!!. I knew i shouldnt have done this as per past experience ,tis best to wait for the 2nd rev on a new release. Cheers

@trent6gol THX for your all help, but on my part off - topic (the above, shell "prtsc" were all I made via IPMI, It was made from a Supermicro + pfSense unit, which is about 3,400 Km from me edit: Advantech is a thousand-year-old company, I see you don't know has a huge reputation in industrial automation! by the way, icurrently all stuff is made in china, and we spoiled it and it’s a suck now