RBR50 Access Control randomly blocking approved devices on V2.3.1.60
RBR50/RBS50
Hi,
After upgrading v2.2 to 2.3.1.60 firmware (both RBR50 and RBS50), some devices with already approved/allowed MAC addresses (wired and wifi) are blocked in the Access Control panel. Some I can un-block but after a couple of minutes the router block them again, and others I can't seems to un-block.
I found a similar thread for firmware v2.2.1.210 and tried all the proposed solution (assign them a static IP, etc) but nothing seems to work.
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
Did you reset the router to factory settings after the firmware flash?
New firmware sometimes introduces changes that are not compatible with the old configuration.
So while it isn't guaranteed to fix problems a factory reset is the first thing to try if you have issues with new firmware.
Maybe that discussion also suggested that, it is too long to read all the way through it.
It might also help if you told people what the modem is in front of this router. The model number could be useful. Is it, by any chance, also a router, with a set of LAN ports on the back?
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
>Did you reset the router to factory settings after the firmware flash?
Yes, of course. I even reset it two more times. The issue disappears for a while, then come back.
What's strange is that is always happen with an old device (wired, a Vizio TV) and a new recently added device (Blink XT2 camera). And after the firmware upgrade. Bummer...
> It might also help if you told people what the modem is in front of this router.
Not sure what has to do with this issues, but here it goes:
Arris Touchstone TM1602A DOCSIS 3.0
The Internet Provider is Spectrum (ex Time Warner)
> , also a router, with a set of LAN ports on the back?
The router is the RBR50 with one RBS50 satellite. It has 4 LAN ports, but since I have too many wired devices, I only connect one RBR50 LAN port to a "D-Link 8 Port Gigabit Unmanaged (DGS-108)" Switch.
All my wired devices (including the one that it's randomly blocked) are connected to the switch.
> It might also help if you told people what the modem is in front of this router.
Not sure what has to do with this issues, but here it goes:
Arris Touchstone TM1602A DOCSIS 3.0
The Internet Provider is Spectrum (ex Time Warner)
People often turn up here talking about their "modem" only to reveal on questioning that they have a router/modem combination. In that case, they can strange connection behaviour because they have two routers on their network and can get sucked into "double NAT" hell.
All my wired devices (including the one that it's randomly blocked) are connected to the switch.
Have you tried connecting the troublesome device to the router? It should not make any difference, but you never know.
As an experiment, have you tried disabling access control completely?
Do the router's logs offer any clues?
If it is possible, have you tried fixing the IP addresses for the troublesome devices and then reserve them in the router.
You may have tried all this stuff. I am just throwing around the few ideas that come to mind.
I'm a bit surprised by that IP address range. 192.168.0.X is normal used on Netgear modems. Routers do 192.168.1.X by default. Perhaps you set it that way for some reason.
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
> People often turn up here talking about their "modem" only to reveal on questioning that they have a router/modem combination...
I had that combination before (ATT gateway/router + my previous router), and yes, took a while to setup and program both NATs. But I did it and it worked. Then, I switched to Spectrum and at the same time decided to have a mesh network at home, so I bought the RBR50 Orbi.
>Have you tried connecting the troublesome device to the router? It should not make any difference, but you never know.
Hummm..I'll try but agree with you, it shouldn't make any difference. Also it'll fix the wired device, *not* the new one through WiFi which is the most important (is the front door Amazon Blink XT2 security camera).
>As an experiment, have you tried disabling access control completely?
If I disable the access control of course it work! Nothing to be 'blocked' 🙂
One of the reason I bought the Orbi RBR50 IS becuase of the access control through MAC address. Without this I'll expose more my network to hacking. Unfortunately I have a couple of WiFi old devices that only support WEP, an old standard very easy to hack. I remember a friend of mine showing me how easy is to get the passkey from WEP devices! So I decided to enble MAC protecion just in case. Remember, Access Control worked fine with previous firmwares.
>Do the router's logs offer any clues?
Good idea, I'll enable the log and look at that, although I'm not expert so not sure if it'll help me fix the issue.
> If it is possible, have you tried fixing the IP addresses for the troublesome devices and then reserve them in the router.
Did that already, was one the the many suggestions on the other similar thread
> You may have tried all this stuff. I am just throwing around the few ideas that come to mind.
Thanks! I apreciated.
> I'm a bit surprised by that IP address range. 192.168.0.X is normal used on Netgear modems.
Historical reason (old windows network default). It shouldn;t matter in a well behave router. And since I have dozen of devices and most them with reserve fixed IP, changing them to 192.168.1.X can be a time-consuming task. I rather not unless some Netgear technician assure me that this is the issue with the new firmware (remember, my blocking issues began after upgrading to the new firmware).
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
There was another thread recently about Access Control that implicated the "Orbi app" as causing issues. (search?)
Are you using the app, or only the web administration?
I have only messed around with Access Control a little (depending on my devilishly complicated password to keep people out), but it came as a surprise to me that there was a table of blocked devices so far down the screen that I had never even seen it.
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
> Are you using the app, oronlythe web administration?
Never used the App, only web and locally/intranet (192.168.0.1)
>I have only messed around with Access Control a little (depending on my devilishly complicated password to keep people out), but it came as a surprise to me that there was a table of blocked devices so far down the screen that I had never even seen it.
Blocked devices are shown in red (and labeled "blocked') in the first Access Control table, at the beginning of the screen. Impossible to miss. Also in the table at the bottom you mentioned.
Anyway, thanks for your help. Maybe it'll be fixed in the next firmware update.
> I'm a bit surprised by that IP address range. 192.168.0.X is normal used on Netgear modems.
Historical reason (old windows network default). It shouldn;t matter in a well behave router. And since I have dozen of devices and most them with reserve fixed IP, changing them to 192.168.1.X can be a time-consuming task.
I am confused about this in relation to the "factory reset". Specifically, are these 192.168.0.x IP addresses "fixed" by means of (1) being assigned in the Orbi LAN Setup table, or (2) being set to "static" rather than DHCP in the devices themselves? When I do a factory reset, my Orbi comes up as 192.168.1.1 on the LAN side and I have to enter all of the IP assignments, which is such a chore that I now have them set up as a text file that I dump into a telnet session. If you have typed these assignments in each time you did a factory reset, they could just as easily have been typed as 192.168.1.x rather than 192.168.0.x.
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
true, but then I have to go to my 3 NAS, 3 PCs and change their static IP (there are not DHCP). Currently my NASs/PCs has fixed IP 192.162.0.100/1/2, and PCs 192.162.0.200/1/2
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
Thanks for the explanation. You are changing the default of 192.168.1.1 to 192.168.0.x each time. I was concerned that maybe you were doing a "reset" but not a "factory reset". Geez. What a mystery!
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
This has been enlightening for me in another way: I had thought that "Access Control" pertained only to WiFi devices. Fascinated to learn that even wired devices can be blocked. Not that I am ready to do this yet, but Access Control would prevent someone from getting at the Orbi administrative web site even if they brought a laptop into my home and plugged it in. (Yes, they could then do a factory reset, but that would leave ample evidence of tampering.)
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
I don't suppose 0.17 and 0.24 are inside the DHCP range? In the past, I set my DHCP range from 2 thru 254 and "assigned" IP right in the middle to specific devices. These days, I assign devices IP's that are not in the DHCP range. Cannot see that it made a difference, but it's something to ask about.
Re: RBR50 Access Control randomly blocking approved devices on V2.3.1.60
No, I don't think it has anything to do with the random blocking I (an others) are experiencing.
The devices I'm showing (x.x.0.17 and x.x.0.24) are the ones currently giving me trouble, but other devices too sometimes are randombly blocked (not as often 'though).
