Webgui incorrectly reports "The system is on the latest version".
In some circumstances the dashboard can report that the system is on the latest version when in fact the pkg system is unable to connect to the repos.
This falsely implies good connectivity when it should report "Unable to check for updates".
It's not clear exactly when this happens but I have seen it at first boot of a fresh install.
Updated by → luckman212 about 3 years ago
Yep I hit this one a couple of days ago, on whatever snap was latest as of 9/5
pkg goes braindead in some way if there's a connectivity problem via the default route. In my case I was configuring a new SG-3100 for a remote site. I set the WAN interface to the static IP of the remote site so I could ship it out "plug n play" -- but in order to run updates and grab the openvpn export package I programmed opt1 as a temporary DHCP WAN via my mobile hotspot.
Even after making opt1 the default gw, as well as making use of PiBa's new "default gw via gateway group" feature, pkg remained borked and said "you're on the latest version" and was unable to view anything in Package Manager either until a full reboot.
I wish I had more time to play around and figure out why but that day I had to get it out the door...
Updated by Max Leighton 12 months ago
- Status changed from Feedback to Resolved
built on Thu Oct 29 07:01:19 EDT 2020
Received "Unable to check for updates" instead of "Up to date" as seen on 2.4.5p1
Marking the ticket resolved.