Which means that valid USB boot drive with the good firmware etc doesn't auto boot except if the admin interrupts the boot process from the console, and types in the command 'run usbrecovery' ....
So, I was wrong. Some manual manipulations are needed then. https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html is clear about it.
@iantmarshall Don’t worry, I got caught in Captcha hell last weekend and couldn’t’ even download the thing, and ended up giving up in disgust and finally managing to track down a direct link to the images to do it manually. It is ridiculous. If someone can’t manage to download an image and create their own USB stick I don’t think they’re the market for pfSense quite frankly.
I had to use the dropdown box and go from 2.7.0 to 2.7.1. After that update completed I went to 2.7.2, It would not allow an update from 2.7.0 to 2.7.2.
After the update to 2.7.1 the admin screen still said I was on the current release.
Otherwise it went smoothly and quickly. The processor in the Hunsn (passmark about 2400) made it fly relative to my older slower pcs from the past.
Yes I would probably just reinstall 24.03 clean. However you may be able to upgrade from there by setting the ranch back to 22.05 and then force reinstalling the key packages:
FWIW I think that's "normal"...have seen that on all the routers I've updated so far. It's noticeable because it seems to take a while to work through them...at least I don't recall seeing that on any previous update.
re: Config History, note pfBlocker updates the config file with a timestamp at every cron interval so it can pretty quickly push out history if it runs at the default of hourly.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.