Pfsense 2.2.2-Release running on FreeBSD 8.3-Release - something is very wrong
-
What I did: I upgraded via the WebGUI then pfsense rebooted.
Dashboard now shows:
2.2.2-RELEASE (amd64)
built on Mon Apr 13 20:10:22 CDT 2015
FreeBSD 8.3-RELEASE-p16I am getting [ There were error(s) loading the rules: pfctl:DIOCADDRULE: Operation not supported by device - The line in question reads [0]: ] notices on the webgui.
When I look at packages, I see pfblocker but not pfblockerng.
Any idea how to get the machine to work on 10.1-Release?
Also - in terms of hardware this is on a Supermicro A1SRi-2758F. I have IPMI console access, but if I reboot the box, my VPN/ access to the LAN goes down.
-
Could the machine be booting from a different device than pfSense was updated on?
It's been a while but I seem to recall that my system running from USB stick would boot from one but load pfSense from the other (if two where plugged in).
Certainly other will know more about this than I.
-
Highly unlikely since there is only one bootable device in there. I did reboot so the SSD it is on is functioning.
-
ys i have had this issue, login into SSH, select upgrade from console and manually feed in the url of the appropriate image from the below link and let it reupgrade and the next time it comes back after a reboot it should be fine
-
OK got to a slightly better place. Here is what I did:
1. Connect directly from my workstation via OpenVPN
2. Load Supermicro IPMIview and open a session (console was not receiving input)
3. As soon as the OpenVPN server came back, use IPMIview to connect to the console - this is faster than the webui
4. Select Upgrade from Shell then autoAfter the reboot it now says:
2.2.2-RELEASE (amd64)
built on Mon Apr 13 20:10:22 CDT 2015FreeBSD 10.1-RELEASE-p9
Also the warning messages went away and the console is functional again.
-
ys i have had this issue, login into SSH, select upgrade from console and manually feed in the url of the appropriate image from the below link and let it reupgrade and the next time it comes back after a reboot it should be fine
Looks like you were typing this as I was.
SSH was locked out, as was the console. So I did the above procedure. Not the best but hopefully helps someone.
-
I had the same issue after updating from 2.1.5 to 2.2.2.
The dashboard show the OS updated, the widgets had a new look but the system never really rebooted. The old kernel was still being used. Uptime was the same:
–------------------------------------------------------------------------------------------------------------------------------------------
Version 2.2.2-RELEASE (i386) built on Mon Apr 13 20:10:33 CDT 2015
FreeBSD REDACTED 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Mon Aug 25 08:25:41 EDT 2014 root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386You are on the latest version.
Platform pfSense
CPU Type Intel(R) Pentium(R) D CPU 3.00GHz
Uptime 238 Days 23 Hours 24 Minutes 25 SecondsI tried multiple times rebooting via the webGUI it didn't work. I ended up having to push the power button on the server to get a clean shutdown and reboot. Then the Uptime looked fine. Error message went away. After login, pfSense said that it was regenerating SSH keys. This procedure worked for two server updates.