NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7300 DST, QOS, Automatically update performance optimization database fails
Is there a setting that I need to change to get the QOS database update to work? When I click "Update Now" to check for new data it returns "Attempting to connect to Netgear Server. Please Wait..."...
It allegedly does also mitigate the vulnerability in question. But it is beta, which is why we don't get them as easy as we wish since there might be side effects.
I won't be able to test and document the outcome soon since I am in the process of replacing mine. It developed erratic behavior after 11 (!!!) months use and it's a pain to get an in-warranty replacement.
Others have also received the firmware replacement and will be able to verify that or if both issues are fixed and if there is a side effect.
Testing is easy and documented:
Read following:
"UPDATE: December 10, 2016 11PM ET. "
Here the POC:
https://www.youtube.com/watch?v=kOZs90BGPFk&feature=youtu.be
strubinsky wrote:
But it is beta, which is why we don't get them as easy as we wish since there might be side effects.
Netgear clearly wants to get the patches out there ASAP, and I'm told that releasing security patches as beta is the quickest path.
The definition of 'Beta' software is that it has not been fully tested and is not guaranteed to be as error free as we consumers can and do expect. Beta is not ready for prime time yet or it would be called 'Production'.
There might be the case that a few 'crappy old' errors are replaced by 'shiny new' ones but after the regression test/fix cycle succeeded it goes prod. You don't give beta to an end-user because they don't care what it is: If it fails somewhere they start yelling 'bah humbug' and flock to their facebook. We are those who are aware of the potential that we might experience minor up to major side effects aka. it is NOT yet the final version and we will replace our betas to prd after it was released.
That is at least my humble opinion and I am sticking to it.
strubinsky wrote:
That is at least my humble opinion and I am sticking to it.
It's certainly aligned with my understanding of "beta" too.
But it is not unusual for Netgear to initially release security fixes as "beta". There have been several ReadyNAS patches released that way over the years, and some didn't reach production for many months.
Again, my understanding here is that making them "beta" allows Netgear internal processes to be bypassed, getting the fixes into the field more quickly. It can get in the way for some business customers, who often have policies that don't allow deployment of beta software.
FWIW, I suspect full regression testing of the patches is probably one of things being skipped. Though usually these fixes are very targeted, so side effects aren't that likely.
That is what I was afraid of ... That one fixes the security issue but breaks android connectivity (*android Kit Kat and newer) craaaawwwwwwwwllllls! ) and so even if I couldn't update QoS database I cannot use it as the droid based hardware is usless to all when its using 1.46.xxxx
Will you experience problem when you stay on the 1.0.0.45 fw?
I venture to disagree!
I received my replacement, updated to V1.0.0.46_1.0.13
and received:
Detection Database Update Assistant A New Detection Database is Found. Do You Want to Upgrade to the New Version Now? Current Detection Database Version: v1.46 New Detection Database Version: v1.80 I'm having same issue and need the firmware beta to fix the problem so I can update the performance QOS database. ElanieM can you send to me?
