NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Access Control randomly blocking approved devices on V2.2.1.210
RBR50
After upgrading to the V2.2.1.210 router firmware, i'm finding that devices that have approved MacID addresses and have been previosly on the network for months are suddenly being blocked in...
It's meant as a work around solution for now until NG gets the bug fixed.
mc64 wrote:
"Manually install firmware and perform factory reset?" That's not really a working solution. I've *been* a network engineer and that's a lame response for terrible QA.
FURRYe38 wrote:
It's meant as a work around solution for now until NG gets the bug fixed.
mc64 wrote:
"Manually install firmware and perform factory reset?" That's not really a working solution. I've *been* a network engineer and that's a lame response for terrible QA.
As much as I agree with you, this may in fact be the first time in history this actually worked. As of today the problem still hasn't reappeard. But i'm checking twice a day, as i'm skeptical as well.
Keep us posted. If NG knows about it, hopefully it should appear in next FW update.
qtschlepper wrote:
FURRYe38 wrote:
It's meant as a work around solution for now until NG gets the bug fixed.
mc64 wrote:
"Manually install firmware and perform factory reset?" That's not really a working solution. I've *been* a network engineer and that's a lame response for terrible QA.
As much as I agree with you, this may in fact be the first time in history this actually worked. As of today the problem still hasn't reappeard. But i'm checking twice a day, as i'm skeptical as well.
That's not a reasonable workaround IMO. I've worked for software product companies, IMO, QA/relase process needs serious improvement. The bug fix should be a priority and I don't see any indication that it is. As a 22-year veteran in this industry, I'm appalled.
Well untill next FW update, users can use the work around. not the first bug nor probably the last.
Good Luck.
Or users can go elsewhere, i.e. another vendor. It's probably what I'll do.
Good Luck then. Enjoy. :smileywink:
Was wondering how yours is working for you?
qtschlepper wrote:
FURRYe38 wrote:
It's meant as a work around solution for now until NG gets the bug fixed.
mc64 wrote:
"Manually install firmware and perform factory reset?" That's not really a working solution. I've *been* a network engineer and that's a lame response for terrible QA.
As much as I agree with you, this may in fact be the first time in history this actually worked. As of today the problem still hasn't reappeard. But i'm checking twice a day, as i'm skeptical as well.