NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Houston, we have a problem. RBR50 F.W. 2.5.1.8 - SSID Renaming not sticking
Just manually updated the firmware to 2.5.1.8 from 2.3.X.X (can't remember the last two numbers). My biggest problem is that after renaming the 5GHz SSID by using the Telnet, config set wla_ssid=...
nuclear_bullet wrote:Just manually updated the firmware to 2.5.1.8 from 2.3.X.X (can't remember the last two numbers).
My biggest problem is that after renaming the 5GHz SSID by using the Telnet, config set wla_ssid="YOUR 5GHz SSID NAME" and config commit, then, reboot, DOES NOT STICK
...
So after some time with the 5GHz SSID set, it would revert back (wla_ssid == wl_ssid).
...
Is anyone else experiencing this? Why hasn't Netgear given us a choice to name the 2.4GHz differently than the 5GHz? Is it because part of their mesh algorithm does a hand-off between 2.4GHz and 5GHz radios?
Yes, others are experiencing the same problem with the latest FW v2.5.1.8. It's a well kown Orbi restriction that it doesn't make this feature available via Web UI for advanced users, but there's a workaround if you're adventurous: Separate WiFi/SSIDs 2.4GHz and 5Ghz bands on Guest Network.
Configuration of the SSIDs via tel net is not generally supported by NG. Nor is separation of SSIDs from Smart Connect.
All configurations of the wifi radios need to be done thru the web page on the RBR.
NG and Orbi have kept policy and there intended design to only have a single SSID name and PW. Letting the system and connected client device chose which frequency to connect too. For the most part it's up to the client devices to pick which frequency they connect too for those that are dual band supporting.
If this doesn't meet your desired configuration needs, Orbi may not be something that suits your needs.
nuclear_bullet wrote:Just manually updated the firmware to 2.5.1.8 from 2.3.X.X (can't remember the last two numbers).
My biggest problem is that after renaming the 5GHz SSID by using the Telnet, config set wla_ssid="YOUR 5GHz SSID NAME" and config commit, then, reboot, DOES NOT STICK
Strange thing is, after a reboot, the debug menu automatically turned off the "Enable Telnet" flag that was set in order to Telnet into the Orbi to issue the config set command.
The 5GHz SSID would show up, my wireless devices will connect to itt and get network access, but after some time the 5GHz would disappear altogether and the SSID of the 5GHz will revert back to whatever was globally set (Which is my wl_ssid 2.4GHz SSID)
So after some time with the 5GHz SSID set, it would revert back (wla_ssid == wl_ssid).
My RBR50 is in AP mode, and I have two RBS50, and I manually went into each web interface for each IP address of the RBR/RBS/RBS setup I have, and uploaded the 2.5.1.8 firmware of its respective type (RBR prefix firmware for the RBR and the RBS prefixed firmware file for the satellites).
Is anyone else experiencing this? Why hasn't Netgear given us a choice to name the 2.4GHz differently than the 5GHz? Is it because part of their mesh algorithm does a hand-off between 2.4GHz and 5GHz radios?
I came from the Asus-world of Mesh radios and I don't understand why Netgear does not allow us to give a unique name to the two different SSIDs.
And where is this Tri-Band function? For the 5GHz radio, I don't see an option to set the upper 5GHz (5.8GHz) bands. All I get is the lower 5GHz band.