Here is a little guide from a nightmare I encountered whilst trying to perform a maintenance update on a pfSense router... I hope my pain and suffering can help someone else :').
DO NOT MAKE MY MISTAKE - CREATE A BACKUP FOR YOUR PFSENSE SETTINGS AND STORE IT LOCALLY BEFORE UPDATING.
pfSense DOES create a backup of settings before updating, but accessing it can be problematic to say the least... (see below)
Context:
I initiated system reboot and upgrade via the pfSense web UI at 1pm on May 15th. Everything seemed to go well in the web UI, until it restarted and then got stuck reassigning the network interfaces.
Looked like the update was successful but got confused when it got to reassigning the interfaces (aka which network interfaces were associated with which network config files previously created) resulting in the boot process being interrupted and not completed, meaning no wifi.
To fix, connected to the pfSense box directly via serial (details at end) & navigated to /cf/conf/backup/ and did a ls -lah to find the last auto-backup xml file and see which network settings were assigned to each interface.
By cross-referencing with the previous backup’s XML data of <interfaces> , it was determined that these were the previous assignments:
note: for opt3&4, it is ixl0 & ixl1, NOT ix10/ix11 (is an l and NOT a 1)
extract from “config-XXXXXXXXXX.xml”
After reassigning the network interfaces, all seemed to be well and the box booted without any noticeable issues into the new OS.
From here, I reconnected in powershell by IP via SSH to check it was working, and then accessed the webUI. 🥳
…I can finally breathe again.
Connecting Via Serial Cable (older tutorial here)
get micro-usb to usb cable
plug micro-usb end into pfsense port labelled “CONSOLE”
plug usb end into laptop usb port. may need to try a few different ones if the steps below don’t work.
navigate here & download the CP210x Universal Windows Driver (direct download link)
unzip it, right click on
silabser.infand click “install”once installed, open device manager (windows). there should be a new option called “Silicon Labs CP210x USB to UART Bridge” or similar. The COM[X] at the end will vary depending on which of your device’s serial ports are already in use
download & open puTTY, and create a session with the following settings, replacing COM6 with whatever COM[X] your device listed as being open to communicate with CP210x in device manager
go to session → logging and track all output to a log file saved locally on your machine
click “open” and session should begin.
Alternative solutions
Thankfully a restore point was (and should, by default on pfSense installations) automatically made right before the update, meaning if worst comes to worst, we could:
copy the last restore point (config file, found at
/cf/conf/backup/) to local machine by: turning on the putty output logger, then opening a session & navigating to the config file &cat-ting it, saving the output to the local machine. Then:EITHER completely re-install the 22.05 version of pfSense via USB flash, get network settings reset, then SCP the restore point config file to it and assign it as settings OR used webUI backup option to reload the settings.
OR try and roll back to the previous version (22.05) by assigning the network interfaces randomly and getting to the pfsense options screen, selecting option
15) Restore recent configuration, and then using the backup config file as the desired settings.in case of further panic... here is a link to further troubleshooting. I wish you well on your journey, and hope it is substantially shorter than mine was 🙃😭.
