Why is restoring from backup more difficult then it should be ?
I did an ooopsy last night, I wanted to upgrade to the latest V4.X.X firmware to fix the Log4j.
I by mistake took the V3.X.X => https://community.tp-link.com/en/business/forum/topic/514452 unless I read this thread wrong I can't seem to find V4.X.X with the Log4J there was a beta but that one is strike through , there is V5 but I don't want that ,... anyway long story short I donwloaded a bunch and in the end mistakenly install V3.x.
Anyway so I updated again to V4.X directly from the V3 gui ( love that not needing to have cloud access enabled to update Firmware )
but my real issue is upon restoring. ( I didn't try to restore on V3 , when I noticed my mistake , I upgraded directly to V4 ) on V4 I tried to restore.
- Why can't there be an option on on of the first screens of the wizard => restore from back up ? that would have helped.
- Why can't I access my autobackups from the USB stick that I'm using , I have a bunch of backups there but I can't load them from the stick when I need them ?
In the end I restored from a backup from my local computer, via the maintenance tab.
For the upgrade
- I'm back on OC200 version 4.4.6 (1.9.3 Build 20210914 Rel.39903) => so where is the Log4J version of the V4 version
(I'm aware that at the time of writting this 4 CVE's weere detected and that 2.17 is needed , and no 2.17 fix is there, at least 2.16 would already ease my mind).
again I'm looking here (unless I'm blind I don't see a V4. fix anymore for the OC200 ):
- Omada SDN Controller:
Omada_Controller_V5.0.15_Windows (Beta) Omada_Controller_V4.4.6_Linux_x64.tar (Beta) Omada_Controller_V4.4.6_Linux_x64.deb (Beta) OC200(UN)_V1_1.14.1_20211213 (Beta) -- Built-in Omada Controller v5.0.21 OC300(UN)_V1_1.2.4_20211213 (Beta) -- Built-in Omada Controller v4.4.6
Here are the official releases for Omada Controllers: