NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBE971 V12.1.10.12 - satellites do not broadcast the IoT SSID (regression from V9.13.x?)
System: RBE971 router plus 2x RBE970 satellites, both on wired backhaul, both showing Good. Firmware V12.1.10.12_5.3.16. IoT network enabled, 2.4 GHz only, WPA2-PSK. Main SSID is WPA2+WPA3.
Problem: the IoT SSID is broadcast only by the router. Neither satellite broadcasts it. The main SSID is broadcast by all three units normally.
Evidence 1, a WiFi scan run from an ESP32 device sitting about 20 feet from one satellite, in a detached outbuilding:
Main SSID from that satellite's BSSID: -39 dBm.
Main SSID from the other satellite: -75 dBm.
Main SSID from the router: -80 dBm.
Backhaul SSID (NTGRBH_...) from all three units.
IoT SSID: exactly ONE BSSID, the router's (its radio MAC with the locally administered bit set), at -80 dBm. No IoT BSSID from either satellite.
Evidence 2, the router's own Attached Devices page: 40 of 40 clients listed as IoT 2.4GHz are connected to the Router, 0 to either satellite. Main-SSID 2.4 GHz clients do attach to satellites, so the satellite 2.4 radios themselves are working.
Impact: every 2.4 GHz-only IoT device in the house has to reach the router no matter where it sits. Two ESP32 devices in the outbuilding are stuck at -80 dBm on the router and drop constantly (measured: 458 availability flips in 24 hours, unreachable for 16 of those 24 hours), while the satellite 20 feet away offers -39 dBm on the main SSID. Power cycling the devices does not help: on a fresh boot they still associate to the router, because the IoT SSID is what they are configured for and the router is the only AP broadcasting it.
A 970-series user reported on V9.13.1.2 that the IoT and Guest SSIDs were available at satellites, which suggests this changed somewhere in the V12 line.
Questions:
(1) Is IoT SSID broadcast from satellites supported on the 970 series, and is this a known regression in V12.1.10.12?
(2) Is there any setting or procedure to get the satellites to carry the IoT network? Both satellites are wired and show Good, and a satellite power cycle changed nothing.
(3) If it is not supported, is a fix planned? With transmit power control removed from the firmware there is also no way to bias clients toward the satellites.
Thanks.
15 Replies
How was the system updated in FW? Automatic or Manually?
RBS first then RBR lastly?
How are the RBS ethernet connected to the RBR? Directly behind the RBR or is there any LAN switch in between? If so, brand and model# please?
What channels are you using on the RBR?
Is Guest Network seen from the RBS?
I'll check into this. I don't use IoT much so I wouldn't have seen this myself.
A few days ago I instantiated an IoT network constrained to 2.4 GHz and of the three devices I changed to the IoT network, 2 connect to a satellite (RBE970) and 1 connects to the router (RBE971) - all seeing XXXXX-IoT SSID. Running V12.1.11.10 updated manually, first to the satellites and then to the router. No probs, works great. Suggest you update to the latest firmware V12.1.11.10
krgoodwin Great feedback, thank you.
jsteele82 Yes update your system to more recent version of FW:
New - RBE970 Series v12.1.11.10 Firmware Release - WW Region | NETGEAR Communities
After updating power cycle the system OFF then back on. Give about 10 minutes with IoT enabled then test again.
After you had enabled the IoT network, how long did you wait after you applied the change to do a wifi scan of the signals at the RBR then RBS?
Can you do another scan if you have not updated the system yet?
Also how did you enable the IoT network? Using the RBR Web page or Orbi app?
Did you give a custom IoT SSID name or use the default one on the RBR?
I did the update manually. I can't recall whether I did the satellites first or the router first.
The satellites are not directly behind the router. There is an unmanaged TP-Link TL-SG105S-M2 2.5G switch in the backhaul path. That switch is there because of an earlier problem in this same firmware line. V12.1.10.12 broke wired backhaul through my managed Araknis switch, both satellites fell back to 5GHz, and they would not hold wired no matter how the switch was configured. Adding the unmanaged 2.5G switch fixed it. Both satellites have reported Wired and Good since.
Channels: 2.4GHz is fixed on 6, 5GHz is on 40. 20/40MHz coexistence is enabled.
Guest network: it has not worked from the satellites here either, and that predates this. So it is not only the IoT SSID. Neither secondary SSID has ever reached my satellites.
How I enabled IoT: the router web page, not the app. Custom SSID name, not the default.
How long before I scanned: months. The IoT SSID has been up and in use by about 40 devices for a long time, so this is not a propagation delay.
I have not updated, so here is a fresh scan taken today from the same spot in the outbuilding, about 20 feet from one satellite:
Main SSID from that satellite: -50 dBm.
Main SSID from the router: -80 dBm.
Main SSID from the other satellite: -80 dBm.
Backhaul SSID from all three units.
IoT SSID: still exactly one BSSID, the router's, at -81 dBm. Nothing from either satellite.
On updating to V12.1.11.10: that release is listed as WW Region. I am on V12.1.10.12, which is listed as NA Region Only, and the router's online check reports no new firmware for the router or either satellite. So I don't think I can take that build without cross-flashing a WW image onto NA hardware, which I would rather not do on a house that runs locks and an alarm.
krgoodwin, are you on a WW region unit? If the fix is only in the WW branch, then the question for NETGEAR is when it lands in an NA build.
jsteele82 V12.1.11.10 WW encompasses the NA region.
To get the IoT and GN working correctly on current version of FW, be sure that you change the default SSID name of each network to something different from the default one. After making changes, reboot the system and those two networks should become accessible. I use custom names on mine and networks work seen and accessible.
FYI, there are known issues with using Managed switches with Orbi systems and having the RBS ethernet connected to these switches. You can get them to work however a switch configuration IS needed on the switch to have the RBS work fully:
Be sure you wireless connect the RBS first to the RBR, then ethernet connect them.
I helped NG a couple of years ago to narrow the issue down on these managed switches.
As far as I know there is only ONE version of the firmware. Only ONE version is supplied by Netgear at https://www.netgear.com/support/product/rbe972s The only difference in Installation Guide for North America versus Europe or APC regions as shown on this firmware update page is the type of power adapter. Has nothing to do with the firmware. V12.1.11.10 only existed from July 13, 2027 to July 28, 2027 (read as 15 days) and as far as I can remember was never intended to be used as reiterated by Netgear. The last firmware specifically marked for NA prior to V12.1.10.12 was V9.12.4.16 in July 2025 with 3 intervening firmware versions listed with no geographical constraint (V9.13.2.1, V9.13.1.2 and V9.12.5.3). I see no mention of a WW region anywhere in the firmware listings. Guess I am still trying to figure out what a wall wart has to do with firmware but I am always open to being educated.
BTW - All the detailed instructions I have in addition to being specifically told by Netgear is to install the satellite(s) first and then the router. I have two satellites and had no problem installing V12.1.11.10 accordingly. I extinguished the candles once I confirmed everything was working (lol).
Update: flashed all three units manually to V12.1.11.15 (the Sept 4 release), satellites first, router last. Both RBE970s came back on wired backhaul, status Good. Then a full power cycle, router first, and waited.
Result is unchanged. The IoT SSID (custom name, not the default) is still broadcast only by the router. A WiFi scan from a device within range of both satellites shows each satellite broadcasting the main SSID and the backhaul SSID, but no IoT BSSID. The router's Attached Devices page shows 31 of 31 IoT 2.4GHz clients on the router (RBE971), 0 on either satellite. Main-SSID clients do attach to both satellites normally, so the satellites themselves are fine; only the IoT network is missing from them.
Settings: Enable IoT Network is checked (BASIC > Wireless), 2.4 GHz only, WPA2-PSK. I could not find any satellite-level IoT setting anywhere in the router web UI. Is there one in the Orbi app?
One more data point: on this firmware the Online Update page offers the satellites V9.13.2.1, which would be a downgrade.
Is IoT SSID broadcast from RBE970 satellites confirmed working on V12.1.11.15 for anyone else? krgoodwin, is your IoT network enabled from the router web page or the Orbi app?
Can you try this? Power OFF both RBS. Disconnect one from your TPLink unmanaged switch and directly connected behind the RBR. No switch in between.
Power ON the RBS and then let it sync, give 5-10 minutes.
Check your wifi scanning app for the IoT signal from the RBS...Is your RBR in router or AP Mode?
“Is IoT SSID broadcast from RBE970 satellites confirmed working on V12.1.11.15 for anyone else?”
Yes, I have many devices connected to RBE970 satellites on V12.1.11.15 but I’m on wireless backhaul.
Is your RBR in router or AP Mode?
could not find any satellite-level IoT setting anywhere in the router web UI. Is there one in the Orbi app?
No. WiFi settings are defined on the router and communicated to the satellites. Any change made on the router (channel, security, names, passwords, etc.) is propagated to the satellites automatically.
