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.
29 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.
One challenge here is that vendors do need to be certain that you are claiming your device, and not some other user's device. One common solution is to add bluetooth. Another is to have the device create a temporary wifi network for installation. Both add complexity to the device firmware and installation workflow.
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).
The RS routers still have the ability to turn ON/OFF the LAN access for the guest networks. I am unsure about the IoT network, still have to test it since this feature was only added in the latest firmware in my RS500 router.
IoT network is working on my RS700. Connected two wireless PCs on it and can connect in between them. If I put one PC on the main LAN via ethernet, still can connect to wireless PC on the IoT Network.
- 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.
Did you performed a factory reset on the router and setup from scratch after v.16 was loaded to see if the IoT network with your devices and your phone worked while all connected to the IoT network?
IF the phone and IoT devices were connected on the same network, the phone should have access to these other devices on the IoT network. The IoT network will not block or separate them while on same network.
Be sure your phone was actually connected to the IoT network.
Historically both Main WLAN and IoT Networks are on same subnet and are not blocked or isolated from each other as this would cause a blockage to happen between the IoT devices and mobile devices connected on the Main WLAN and supporting IoT apps to fail to connect. NG has intended this design for the IoT and Main WLAN networks to avoid this issue.
What IoT devices do you have connected on the IoT network?
Did you restart your devices or the router?
I find it puzzling that the RS600 and RS700 manage their IoT networks differently.
- RS600: devices on IoT cannot communicate with other devices on the IoT network nor the primary network.
- RS700: devices on IoT can communicate with other devices on the IoT nework (and on the primary network???)
With the firmware being released so close together (RS700: Dec 19, 2025. RS600 Feb 3, 2026) one would expect them to be very much alike.
Looks like an "oops" at Netgear.
IoT devices could communicate with primary network in my RS500. The RS600 also has the same firmware as the RS500. Not sure what issue the OP has, might be a device/app problem.
Maybe a IoT app or IoT device issue. The IoT Network feature would be the same across all RS supporting routers. Would not be different. All the same base code.
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
Perhaps it would be helpful to repeat this experiment and:
- Also try communicating with devices on the primary network.
- Document the method used to communicate with devices (that works on the primary network and fails on the IoT network).
Thanks everyone for the suggestions. During my two days of messing around with trying to make it work, I really did try many, many, and many different combinations and reboots on all the devices that I was working with. The RS600 is a very solid router when used in a basic configuration, and that's where I'm at. Thanks again for your responses.
Does the IoT device work with it's app if you put it on the Main WLAN?
I'll try this on my RS600 to confirm this...been testing a RS700 so figured the basic configuration will work for all RS series router. It should.
Yes. I added my WiiM amp to the 2.4G IoT and then put my iPhone on the IoT network. They would not communicate and the WiiM app was telling me to connect to the same network as the amp. My phone had no problems getting on the internet from the IoT network. I had to do a factory reset to get amp back on the main 2.4G network. Put my iPhone on the main 5G network and no problems.
added my WiiM amp to the 2.4G IoT and then put my iPhone on the IoT network
Was the IoT network active on both 2.4G and 5G during this test? Some smartphone apps do not function correctly when the phone is connected at 5G.
Does the WiiM amp respond to ICMP (ping) ?
Thank you for bearing with us on this. It is just so strange that users have tested both the RS500 and RS700 and found that they both handle the IoT network as expected.
I had the IoT set to 2.4G only and WPA2.
Sorry, I'm not familiar with an ICMP (ping). As the WiiM was switching from my main network, the setup reported that it had successfully connected to the IoT. The WiiM device uses Bluetooth during the setup from a factory reset and then requires a WiFi connection for further adjustments. With my phone on the IoT network, was when they could not see each other.
Sorry, I'm not familiar with an ICMP (ping).
Worth looking into - googling will lead to useful guides. It is a basic network troubleshooting tool.
With my phone on the IoT network, was when they could not see each other.
I'm wondering if it would have worked if you left the phone on your main network (but connected the WiiM the IoT network).
I think the general consensus is that the IoT and the main network should not be able to communicate with each other. It could be an option, but I want it to be separate.
I think the general consensus is that the IoT and the main network should not be able to communicate with each other.
Definitely not a general consensus. Although CrimpOn initially said it was arguable either way, there is no general agreement that the IoT network should be fully isolated. Instead posters are puzzled about why your RS600 is behaving differently from other Netgear routers with the feature (including the RS500 and RS700).
And other Netgear routers with the feature definitely do allow the devices on the IoT network to communicate with the main network and with each other. I just confirmed this using ping on my Orbi 871.
That said, I do think it would be good to have some more options for isolation. But I think that isolation should not be the default, since the main benefit I see for the IoT network is to maintain compatiblity with older 2.4 ghz only devices and also devices that do not support WPA3 security (which is required for WiFi 7) .
