![]() I removed the max limit on my inboud/outbound queues * Setting the target slightly lower than the real speed because we are missing the Ingress keyword to compensate * Setting the Simple queue limits to Unlimited and the Cake specific limit to my target These steps are apparently not atomic and if step 3 fails - you're screwed.īut I can only get the expected ingress performance by: Always those edge-cases.Īs far I observed the process of updating it works this way: I am possibly the only one here that issued a LE-certificate and performed an upgrade. ![]() Maybe the upgrade did not like that LE-certificate residing somewhere in the void of router-storage omg. Actually the only config change I did before upgrading - and without reboot - was to generate a lets-encrypt certificate (because I had an SUPEE opened for that - now resolved). Then you know if it is caused by the previous version or by the updating. ![]() When you want to be sure, reboot before trying to update. It is still happening in some cases in v7. It would probably have happend when you had only rebooted. Shake my head.Įasy! The config is corrupt and is cleared on reboot. I am always wondering HOW that can be even happen. Or at least in some weird state without IP-address and non-working WIFI (though enabled with default as far I can see). HDevice has apparently reset itself WITHOUT default-config.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |