NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 About device names
Orbi RBR50v2, two satellites. v2.7.4.24. Mac systems Question about device names in the App I always give a new device a name and have had no issues there. Recently I added a new smart hub, (Aqara...
ron111157 wrote:
I'm thinking that blocking by MAC in Access Control setting works on wireless devices, not wired.
That would make logical sense however look at this
It clearly says Wired connection. so either
1. It is misidentified as wired when it is actually wireless
2. One ethernet port has 2 MACs which should not be
Either way it was Blocked so should not of been given Access as the log states.
I agree completely that I shows "Wired" within the block list - but looking through various Knowledge Base articles on Access Control - some specifically state it's used for Wireless connectivity, some say Wired/Wireless - so it may or may not work as expected - based on which KB article you read. I've used other blocks - like blocking websites on NG's products - and the router reports that it is doing so - but really doesn't. So sometimes things report correctly, sometimes they do not.
Again, since it is WIRED (which you say it is and the system says it is) - the best way to keep it from connecting to your network - is to not PHYSICALLY connect it to your network.
Today is "Fun with Orbi Day". I, also, experimented with using Access Control to block a wired device (Epson printer):
Results were puzzling. Even though Access Control and Attached Devices clearly show the printer as Blocked:
- I could print to the printer.
- I could use a web browser to access the printer control panel.
However, when I used the actual printer controls to search for firmware update, the printer complained that it could not reach the internet. Unblock the printer and it searches for firmware update just fine (at the latest already). I will block a desktop computer next and see what happens.
The preliminary conclusion thus far is that "Blocked" is an ambiguous term, and almost certainly does not match what one might expect. i.e. the blocked device cannot originate a TCP connection, but it can respond to a connection established by an Allowed device on the network.
More to come....