Running an RBR50 with 1 x RBS50 backhauled over ethernet. Both running V2.5.1.8.
Is there still a known issue, no real fix for Access Control randomly moving devices to BLOCKED status even when intervening and manually setting back to ALLOW?
Workaround I have in place is having Allow all new devices to connect checked which is obviously not ideal if people go thru all the trouble of adding MACs for approved devices, etc.
Is there still a known issue, no real fix for Access Control randomly moving devices to BLOCKED status even when intervening and manually setting back to ALLOW?
Do you use the Orbi web interface or the Orbi "app"?
When problems are experienced, yes, it's recommended. Changes in FW may cause older configuration to not work right or there maybe lingering FW code from prior versions. Resetting and setting up from scratch is recommended in these cases.
OK - thank you for the feedback. The version of FW on their now is first time upgrade after initially setting these up around 2 months ago. I didn't experience this anomaly until a couple weeks ago.
Did the 'factory reset and then set up everything again' dance work in this case? I just got my RBK50v2 yesterday, and set it all up with explicit access control for all of my devices - later updated to latest firmware, and I'm seeing that the 'allow' state for some of my devices is randomly changing to 'blocked' too. To the extent that I allowed a device this morning in the web interface, and it transitioned to 'allowed', but then - on exiting the access control screen and reentering it, both that device *and* another had moved to 'blocked' even though they were both 'allowed' immediately before.
It took *ages* to set this thing up with all my devices.. last thing I want to do is to spend more hours resetting it and doing it all from scratch again. Is a factory reset + a restore of the settings (saved just before the reset) sufficient? Or do I just stop using access control until this is fixed.
Really bad first impression of the Orbi, I have to say..
With a brand new Orbi, Netgear provides 90 days of "complimentary support" (which is of course, absurd. "Included in the price" is more accurate.) There is a link on the product registration page to contact Netgear support. Maybe it's time for Netgear to earn their money?
Hmmm.. I've attempted to do that - but after spending a significant amount of time entering a really detailed report, pressing to submit the support request just bounced me to a page where it said
"Page Unavailable : Sorry, but the requested page is unavailable due to as server issue."
So right now there's not even any working support email. Which doesn't exactly ease my concerns..
Anyway, shall try again later - maybe the hamsters will have found their way back onto the wheel by then, and the server will be working.
Try this, factory reset the RBR and setup from scratch. Before configuring any access controls, setup IP address reservations for your devices. Save and apply. Then go in and set up access controls. Then see if the block and access works.
Thanks for the reply, but as I mentioned I’m not wanting to do a factory restore and the full setup again. Especially when it’s not guaranteed to work. I want the actual cause of the problem to be identified and fixed at a firmware level. I have a report ready to raise with netgear, but (as mentioned above) their support systems seem to be out of order. Which is also pretty poor, right?
I'm sorry, but I have to second that the 'doing a factory reset and setup from scratch again' is a piss poor solution especially when this seems to be prevalent in older firmware as well. Are users expected to do this every time a new firmware update comes out and/or periodically if this feature quits working?
I will look into sending an official bug report as well.
@thethirdnut, I eventually managed to raise a support request on my side too (been trying all week, only to have the same server error messages - but it's now playing ball).
Reference number 42872221, and as with you I'll post back here if I get some good feedback. Hopefully with two reports (and two sets of data, if they need diagnostic information) they'll be able to get to the bottom of this.
