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.
Thanks all for the replies. I did the Guest Network work-around, but it really would be better if the user is allowed to set different SSID.
If the third 5GHz band is used as a backhaul, then we should at least have the option to choose which SSID to connect to.
I'm not sure why you're catching so much flack for asking this question. I've had an Orbi RBK50 for longer than I'd like to have had, I guess 2 years or something, and after every update I also run the commands for 2.4 and 5 bands... This is the first version that the change hasn't stuck even running config commit. Same here, disabling telnet after reboot. It's a pain in the ass.