2100 :: Upgrade from 23.05.1-RELEASE (arm64) to 23.09 - Experience
-
@netboy Did mine last night. No issues with the upgrade (wait the normal 10-15min). I am aware of this which is not related to it being a 2100:
https://forum.netgate.com/topic/184104/dhcp-weirdness-after-23-09-upgradeAlso a System Patches package update released recently with several patches for 23.09.
-
@SteveITS Just did my upgrade (2100) and it went smoothly and took around 10 minutes!!!
-
I just upgraded my 2100 with no problems. I uninstalled Avahi and pfBlockerNG, rebooted from the USB console, then updated from the USB console. Took about 10 minutes, then reinstalled Avahi and pfBlockerNG and installed the recommended System Patches. Everything appears to be working properly.
Well done Team Netgate!
-
@terryzb I upgraded using the GUI and not thru the console....no special configuration was required for me
-
This post is deleted! -
I have an SG2100 and the update bricked my firewall. I had to roll back to previous kernel and then do a full reset and upgrade AGAIN from the CLI on the console. I seem to have lost all my configs.
-
@whatthehell “full reset” being a reinstall? That wipes the drive. But you can still restore from backup.
-
@SteveITS I tried to do a factory reset but the button press had no effect. After selecting the 3 / 3 kernel I got to the menu where I could do a factory reset ( option 4). Then I rebooted and it was still not starting services etc. I went back to the 3 /3 kernel option, got to a prompt where I ran the upgrade command and that seems to have gotten me back to where the device will reboot. I just need to reset the NAT rules and VPN and I will be back up and running. After the initial upgrade I did last Thursday both the circle and square were rapid flashing.
-
@whatthehell The 2100 button does reset but there’s a procedure:
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/factory-reset.htmlThat is just the config file though not a full reinstall.
-
@SteveITS Yep, I saw that. Me and the paper clip were busy. Didn't work though.