You could force it do that every time but it would delay boot significantly. Check the script used in /etc/rc.initial.reboot.

@stephenw10 perfect answer, thanks. Looking for grunt here…
G

@JustCuriose

Something popped up into my mind when I saw your post :
You didn't mention the 3 letter word that Microsoft now wants to be present : TPM. A physical chip on the motherboard.
Without it, there is no direct access to Windows 11.
Its all (among others) about protecting safe booting - and protecting the boot process.

Checkout Youtube and look for Lojax. I didn't found any in-depth articles (videos) but it's pretty nasty.
On the other hand : if a boot virus is present on your system, some one had to have access to your system, with root rights, and install it. IMHO, the moment they login, the system is already considered 'dead'

Yup, pfSense CE is x86 only and most SOHO routers are not. Did you have specific hardware in mind?

@keyser Thanks for explaining this. 🙏

@stephenw10 Ok, i will think about it.
Thanks

Point releases are usually for security updates or hardware support when a full release is not ready.
You can see what it included in this case here:
https://docs.netgate.com/pfsense/en/latest/releases/23-05-1.html

You can update home/lab installs.

Steve

For anyone else that comes along to see, clock speeds vary wildly depending on PL1, PL2, and PL4. I found setting PL1=9, PL2=10, and PL3=30 to be the best balance of performance (single-threaded for OpenVPN) and heat.

You probably don't need the newer version. And because that is not built against the pfSense kernel it may not load at boot time.

You need to check the bootlog to make sure it is loading and attaching to the NIC.

Steve

It may not read that if the 1.4GHz is a boost speed. On Intel CPUs the turbo speed would be shown only as 1001MHz for example. The additional 1 indicates turbo is active.

I'm not sure how the APU 'boost' might be shown. It may not. It's probably detailed in the APU2 thread though:
https://forum.netgate.com/topic/95148/pc-engines-apu2-experiences

The Compex WLE200NX should work there but there are no internal antennas. And no holes to mount external antennas. An external access point it better in almost every way.

It's been a few versions since I tested it.

Steve

Probably the slightly older chip in he older 1100 was supported by the included driver in Windows 11. A newer chip revision is not so requires a driver update.

I'm not sure why you were directed to the Silabs driver. If that was by us that was a mistake, I apologise.

Steve

So an APU4. Then yes see: https://pcengines.github.io/

Any Coreboot version will boot pfSense though.

Steve

@stephenw10 😊

Check the actual PCI IDs, run at the command line pciconf -lv. Or in Ubuntu: lspci -nv.
There may not be a FreeBSD driver for those NICs.

Steve

You can check the boot log in Status > System Logs > OS Boot. You should be able to see all the NICs detected and attached.

Yup that^. Those numbers are too close to 100Mbps. Check the actual linked speed of all the NICs involved.

@stephenw10 Worked great. Thank you.

The best info there is in Christian's video:
Youtube Video

UPDATE: I tried one more time this time on bare metal - the PCIE 4X connector indeed works with the QNAP 4 port card.

It seems ESX has trouble with the PCIE slot, but native is OK.

Now I have a 12 port router w/ 8 x 1Gbe and 4 x 2.5Gbe.

I'm going to test stability over the next few days.