Want to update to 2.0.2 but "You are on the latest version"
willmc last edited by
I'm running 2.0.1-RELEASE (i386) on the "nanobsd (2g)" platform (each as reported by the dashboard page). If I go to System > Firmware > Updater Settings and choose "pfSense i386 stable updates" (thus setting the URL to "http://updates.pfsense.org/_updaters"), click "Save" and then hit the "Auto Update" tab, it reports:
Downloading new version information...done Obtaining current version information...done You are on the latest version.
If I go back and change the URL to the amd64 version it then offers to update me to 2.0.2-RELEASE, but that's of course the wrong architecture. I see two other people mentioning the same problem in the comments on the 2.0.2 announcement on the blog, but no solution. Does anyone have any idea what I'm doing wrong? Thanks for your help!
I checked the version file on all three of our update mirrors for 2gb nanobsd i386 and they all correctly display 2.0.2 as the current version.
Is there a caching proxy in front of this firewall somewhere that might be returning old/stale data?
NickF last edited by
While the files 'version', 'version-nanobsd-1g', 'version-nanobsd-2g', 'version-nanobsd-4g', 'version-nanobsd-512mb' all have the content '2.0.2-RELEASE', the files 'version-nanobsd-vga-1g', 'version-nanobsd-vga-2g', 'version-nanobsd-vga-4g', 'version-nanobsd-vga-512mb' all have the content '2.0.1-RELEASE'.
I guess the Dashboard System Information widget checks the 'version' file, sees that '2.0.2-RELEASE' does not match the local version, and displays the 'Update available. Click Here to view update.' message.
However, when you then load the System: Firmware: Auto Update page, it uses the platform info (nanobsd-vga-4g) to check, and the 'version-nanobsd-vga-4g' file has the content '2.0.1-RELEASE', which matches your current firmware version, so the Web page displays 'You are on the latest version.'
I have a high suspicion this is correct, as my ALIX box (without VGA) saw the upgrade correctly and upgraded correctly, whereas my Intel box with VGA ran into the same issue as you described.
I think the developers need to correct the version information in the files mentioned above for the auto updating to function correctly for the VGA builds.
Happy New Year!
aha, I didn't check the vga ones, they were wrong for nanobsd-vga i386.
Should be OK now all around.
willmc last edited by
That fixed it. Thanks!