NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi 960 Block Services Not Working
I have setup a Block Services rule on my Orbi 960 and it does not work. I have reserved a specific IP address for my robot vacuum (192.168.1.251). I then went to Advanced -> Block Services turned ...
After going back and forth with support a few times, I received this as a response:
"Thank you for your time and patience. According to the engineering team, the block services in the Web GUI will only block HTTP sites and services. They recommend using the Smart Parental Control instead."Unfortunately, Netgear charges a monthly fee to use the “Smart Parental Controls.” In my opinion, this is a highly anti-consumer practice, especially considering that these are fairly basic router capabilities on a product that costs over $1000.
Sorry for the confusion, no don’t disregard the post, just that reply. There was no way to delete the response, so I edited and put disregard.
The vacuum connects to a cloud service, and I can then access the robot via an app on my phone. With my current testing, I have my phone wi-fi turned off to ensure there is no local access happening. I then open the mobile app and refresh the device to see if there is a connection. If the robot is connected to the internet, I am able to access the device and it appears as "Connected".
The robot vacuum is connected to my IoT wireless network setup in the Orbi.
Re: the experiment, I just tried this, yes you are correct this worked – the robot is no longer accessible via the app, but it is listed under my "Attached devices" on the Orbi UI. If I then changed the Service Blocking to "Never" the device connects and can be accessed via the app. But, if I then change Service Block back to "Always", the blocking no longer works and the Robot continues to have internet connectivity.
Had this worked at all prior to updating the FW on the system?
c3polt wrote:
Sorry for the confusion, no don’t disregard the post, just that reply. There was no way to delete the response, so I edited and put disregard.
The vacuum connects to a cloud service, and I can then access the robot via an app on my phone. With my current testing, I have my phone wi-fi turned off to ensure there is no local access happening. I then open the mobile app and refresh the device to see if there is a connection. If the robot is connected to the internet, I am able to access the device and it appears as "Connected".
The robot vacuum is connected to my IoT wireless network setup in the Orbi.
Re: the experiment, I just tried this, yes you are correct this worked – the robot is no longer accessible via the app, but it is listed under my "Attached devices" on the Orbi UI. If I then changed the Service Blocking to "Never" the device connects and can be accessed via the app. But, if I then change Service Block back to "Always", the blocking no longer works and the Robot continues to have internet connectivity.