Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Ronski]

Under Branch, mines says current stable release (2.7.2), but then says

Current Base System 2.7.0
Latest Base System 2.7.0
Status Up to date.

Odd.

I also read a different article today, but based on this https://www.sonarsource.com/blog/pfsense-vulnerabilities-sonarcloud/#:~:text=pfSense%20CE%202.7.0%20and,1%20and%20pfSense%20Plus%2023.09.

[Alex Atkin UK]

Looking in update for some reason mine was set to Depreciated version 2.7.0, no idea why.  Also seems a typo and they meant deprecated?

Switching to 2.7.2 in there allowed me to update to 2.7.2.

2.7.2-RELEASE (amd64)
built on Fri Dec 8 20:55:00 GMT 2023
FreeBSD 14.0-CURRENT

The Update page is lagging horribly though.

They've been playing with how the repos are managed to avoid the long standing issue of it automatically switching to a new version then the user accidentally installing package updates for that version, before upgrading the core OS. So I wonder if they borked something?

[Ronski]

The other option is the failed update borked something.

[Alex Atkin UK]

Worth noting on mine there are no options to switch Branch after the update, there is only 2.7.2 in the list.

I also keep getting "Unable to check for updates" so I do wonder if something is wrong their end.

[skyeci]

No problems checking update status on mine.

2.7.2-RELEASE (amd64)
built on Fri Dec 8 20:55:00 GMT 2023
FreeBSD 14.0-CURRENT

The system is on the latest version.
Version information updated at Wed Dec 13 20:32:04 GMT 2023

Running a manual update check provides no errors either.

[Ronski]

Mine still thinks its up to date, on both the auto check and manual check, when its not.

[kitzuser87430]

Any ideas how to "force" an update??

[Ronski]

No idea, I was wondering that myself.

[Alex Atkin UK]

https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html

Of course:

Navigate to System > Updates

Set Branch to Previous stable version

Is about as helpful as a chocolate teapot, given all other branches have disappeared on mine.  Of course mine WAS successful so not a problem.

[Ronski]

I found a similar thread from years ago, where eventually the poster set the branch to development, it then allowed them to update, and then go back to stable, but there are no development options, and changing it to the only other options doesn't work.

This morning I just get unable to check for updates.

If it doesn't sort its self out I guess I'll do a back up and then a fresh install eventually.

[Chrysalis]

Run this command on root shell.

'certctl rehash'

Then check again, and it should show 2.7.2.

It is because the pkg system changed and the one they using in 2.7.0 needs updated certificates.

[Ronski]

Thanks Chrysalis, you're a star, that did the trick. Just issued the command from the diagnostic command in the GUI.

Now to see if the update completes.

[Ronski]

Its now updated, but it did get stuck at the rebooting stage, had to power cycle it, but luckily it came back up OK.

[kitzuser87430]

I could not use the dashboard/GUI, ( perhaps my everyday user profile does not have the correct rights)I logged in as an admin via ssh, and run Chris' command.

Updated with no issues.

Ian

[Alex Atkin UK]

I updated my backup router without any issues at all, nothing special, just chose the update from console option.

Other than spending way more time than I should have trying to figure out how to make it work without conflicting with the identical configuration on the main router.  I usually just plug it into the 5G router to do that, but Three were having a moment.

I was completely unaware how easy it is to share your Internet connection on Linux these days.  I just added my on-board NIC to Network Manager (its normally not in use as I have a 10G PCIe NIC) with Method "Shared to other computers" and bam, can use that as the WAN interface with the NAT hiding the main router.

Honestly, half the fight was I constantly kept forgetting I have to connect to the router on the LAN VLAN.  I probably wasted an hour wondering why DHCP wasn't working.  Then the config file I exported from my main router was corrupt, something is off when you backup RRD data.