NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware V.2.5.2.4 Changes SSID Name for SSID Name set for 5G Band
Previously set the default SSID in my RBR50 router and RBS50 satellite to "xxxx xxx 2.4" on the 'Wireless Setting' page of the RBR50, and Telnetted into the router and changed the SSID name of the of the 5gig band to "xxx xxx 5" using the 'config set wla_ssid="xxxx.xxx.5" command followed by a 'config commit' command and a reboot of the router. Same thing was done for the RBS50 satellite. Everything was working fine.
Over the weekend I upgraded the firmware to V.2.5.2.4 on both the router and satellite. The firmware upgrade didn't retain the 5gig SSID name I previously assigned to it, and only kept only the first four (4) characters of the 2.4gig SSID. I've Telnetted into both the router and satellite and set the 2.4gig SSID and the 5gig SSID using the config set wl_ssid="xxxx xxx 2.4" & config set wla_ssid="xxxx xxx 5" commands followed by a 'config commit'. The router and satellite will broadcast the 'xxxx xxx 5' SSID for a few minutes, but then revert to SSID 'xxxx'
This is causing problems with the IoT devices on my network. What do I need to do to create a separate SSID for my 5gig devices with this version of the firmware?
6 Replies
Freway01 wrote:This is causing problems with the IoT devices on my network. What do I need to do to create a separate SSID for my 5gig devices with this version of the firmware?
Manually revert back to the previous firmware and resist the temptation to install new firmware. Or, painstakingly read through all of the posts about "splitting SSID" until you find a method that works and hope that new firmware does not make it stop working (as happened to you).
Many of us who participate in this forum have houses full of IoT gizmos that are perfectly happy with the Orbi WiFi once they get set up. Having only a 2.4G radio, these things cannot detect the 5G signal (just as they cannot detect AM radio signals or 900MHz cordless phone signals). I fear this is another example of the extreme polarization of our society. Some of us believe it is not that hard to get these things connected and others of us sincerely, passionately, believe that the only solution is to have different SSID's.
In my case, a few devices have poorly written smartphone apps that fail when the smarphone is connected at 5G, but work just fine when the smartphone is temporarily connected at 2.4G. This method seems to work:
- Access the Orbi web interface (http://orbilogin.net) using the admin credentials user "admin" and the Orbi router password (not the WiFi password)
- Navigate to the Advanced Tab, Advanced Settings, Wireless Settings
- Uncheck the box "Broadcast SSID on 5G Channel"
This will not affect any devices which are currently attached to the Orbi at 5G. - On the smartphone settings, "forget" the Orbi WiFi
- Search for WiFi networks and select the Orbi WiFi
- Enter the WiF password and connect
- At this point, open the IoT app and go through the steps
- After the device is connected, reverse the steps
Check the box "Broadcast SSID"
"Forget Orbi WiFi"
Search for and connect.
In your situation, the fastest method would seem to be "going back" to the previous firmware, splitting the SSID's, and never updatin g firmware. No devices have to be reconfigured, and you can get on with life.
Thanks CrimpOn, but I want to stay on this version of the firmware. It does a better job if identifying the devices connected to the Orbi then the last version I was up on. For the time being, until Netgear fixes the problem with SSID naming (this happened a couple of versions back also), I'll just reconfigure the IoT devices (about 10 devices) that were using the 5gig band (SSID) and sign into the default name the RBR50 gave as a 5gig SSID. The Orbi assigned SSID isn’t that descriptive, but will do until Netgear fixes their screw-up.
Freway01 wrote:Thanks CrimpOn, but I want to stay on this version of the firmware. It does a better job if identifying the devices connected to the Orbi then the last version I was up on. For the time being, until Netgear fixes the problem with SSID naming (this happened a couple of versions back also), I'll just reconfigure the IoT devices (about 10 devices) that were using the 5gig band (SSID) and sign into the default name the RBR50 gave as a 5gig SSID. The Orbi assigned SSID isn’t that descriptive, but will do until Netgear fixes their screw-up.
The user can specify any SSID in the both the web interface and the Orbi "app", and it will be broadcast by both 2.4G and 5G channels.
It's too late for you, but my practice for the last 15 years has been to give each new WiFi router the exact SSID/password as the one that is being replaced. (a) every WiFi device connects automatically without having to be reconfigured, and (b) if I decide to "go back", I can just plug the old WiFi router back in and every device will automatically connect to it. (My guess is the firware feature that messed with your SSID's stopped at the first space character.)
