NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RS600 latest version, 1.0.6.16 IoT network works like a Guest Network
Well, I got all excited about the new IoT network capabilities in 1.0.6.16. I moved a couple of devices to the new IoT network, and they connected to the internet. Then connected my phone to the IoT network. It also connected to the internet but could not connect to the devices. Works no different than a guest network. Then switched everything back and working fine. What a waste of time and emotion.
3 Replies
Thanks for taking the time to test and report.
There are different philosophies regarding WiFi networks and sometimes it is not clear whether Netgear has a consistent approach.
Guest WiFi, for example, can be implemented for two different reasons:
- To provide a way for "guests" (i.e. transient devices) to access the network without sharing the primary WiFi password.
The Guest network password can be changed at any time or the network itself can be enabled or disabled without affecting
devices on the primary network. (except, of course, when the network falls silent while the WiFi adapter is being restarted with the new settings) - To provide a network for devices that should have only internet access, but not be able to communicate with devices on the primary network.
This is the philosophy that Netgear adopted for the Guest network beginning with the WiFi6 products.
I, personally, prefer the Orbi WiFi5 scenario where the owner decides whether devices on the Guest WiFi network can (or cannot) communicate with
devices on the primary network. Imagine, for example, that members of the Book Club have come over and someone wants to use the printer. If
the Guest WiFi allows communications (right now, I could turn that off when they leave), it's "no problem". None of them know the primary WiFi
password. With newer Orbi products, the owner no longer has that ability.The Internet of Things (IoT) network was created because for YEARS companies have delivered IoT products with poorly written smartphone apps
that fail when the phone is connected at 5G (or 6G?) All that time, customers begged to have the ability to simply turn off the 5G radio signal temporarily,
connect their phone to the remaining 2.4G signal, connect the device, and then turn the 5G signal back on again. Netgear refused. Because the IoT 5G
signal can be turned on or off at will, the IoT SSID provides customers with what they had been asking for. i.e. a way to connect devices with poorly
written smartphone apps.That leaves the philosophy about whether devices on the IoT network should be able to communicate with the primary network or not. There are arguments
for both positions (yes or no). While the first implementations of IoT on the Orbi products allowed communication. It appears that the new firmware for the
RS600 does not. Other RS products? Beats Me.That leaves the philosophy about whether devices on the IoT network should be able to communicate with the primary network or not.
Mine have to (though only during installation). FWIW, this is as much about the device firmware and router firmware as it is the apps. Many IoT architectures use broadcast protocols for discovery, and there are problems when routers do not forward those broadcast packets to other SSIDs on the same network.
I, personally, prefer the Orbi WiFi5 scenario where the owner decides whether devices on the Guest WiFi network can (or cannot) communicate with
devices on the primary network.I think making that an option for the IoT network is a good idea. Though if you really want isolation, you also need to block access to the LAN (which older Netgear routers with this option failed to do).
- To provide a way for "guests" (i.e. transient devices) to access the network without sharing the primary WiFi password.
What I have learn from this experience is that you don't buy a router without reading the manual first. I been looking at Asus routers and they have the features and flexibility on the Guest and IoT networks. Will likely be moving on with the next router unless NG can get their act together.
