I have been having a lot of issues getting my Orbi system (RBR50 and RBS50) and my Sony HT-ST5000 soundbar to play nicely with each other (documented in detail here). The issue can be resolved if I can get all the clients to connect to the Orbi over 2.4GHz, thereby reserving the 5GHz band for the soundbar and the subwoofer to communicate on. I tried reducing the power on the 5GHz network down to 25% and unchecked the "Enable SSID Broadcast" option under Advanced Wireless Settings. I thought that doing so would force clients to use the 2.4GHz connection. However, to my surprise my Mac continues to connect to the 5GHz channel after making the changes and the Orbi is most definitely broadcasting a 5GHz network over channel 36 too as can be seen from the WiFi Explorer app 🤯 For good measure I had removed the network from my saved networks on the Mac as well and so don't know what is happening. I understand that disabling SSID broadcast is not the same as stopping a network and that clients with login information can still connect to hidden SSIDs. However, I would have assumed that after disabling the SSID Broadcast for the 5GHz network and forgetting all Orbi networks on my Mac, my Mac would have no knowledge of the 5GHz network. I would be very grateful if someone could shed light on this. I am specifically interested in the "Enable SSID Broadcast" option and what it is supposed to accomplish in a mesh WiFi environment such as the Orbi. If the SSID for the 2.4GHz and 5GHz network is the same then why does is this option present, that too separately, for each of the networks? CrimpOn, I've been reading a lot of your posts in my research on the subject and so would be thrilled if you could please weigh in on this. Thanks!

Anjadekar wrote:I have noticed that after deleting the network information on the Mac it initially connects over the 2.4GHz network and then switches back to the 5GHz one after a few minutes.My experiment confirms your observation. When I "forgot" the Orbi SSID and quickly searched and reconnected, it did so at 5G. So, I was more deliberate. I "forgot" the Orbi SSID and restarted the phone. It was sitting in my hand with no WiFi enabled, yet the Orbi Attached Devices claimed it was connected at 5G for about 5 minutes. Hmmm. Orbi seems to have a "timer" of sorts and does not drop a device from Attached Devices immediately. Sure enough, eventually the phone dropped off. Entered my phone passcode, went to WiFi settings, connected to Orbi and the phone connected at 2.4G (both the phone and the Orbi report 2.4G). Sat watching for a while, and "Shazam", the phone is now connected at 5G. So, there appears to be a window of time during which a device will remain connected at 2.4G before switching. My guess is that only newer devices that are programmed to "roam" will have whatever software feature it is that enables this behavior. Of course, these are exactly the devices one would be using to set up IoT gizmos. With my colossal level of ignoance and self-confidence I have been assuring people that using the "Broadcast SSID" tactic will enable them to easily set up IoT devices on the Orbi (when the app software is too stupid to work properly on mesh WiFi systems). I guess that advice now has to include, "Don't dilly dally. You've got 2-3 minutes to work with."

I have some great news! I was able to unbrick my Orbi! I used this excellent tip to keep the Mac plugged into the router and then restart it with the reset button pushed down with a paperclip. As soon as the router started and the red light blinked I pinged 192.168.1.1 (while keeping the reset button pushed down) from Terminal and, voila, the red light kept flashing and TFTP mode was activated! I then took the pin out of the reset button and initiated the transfer of the firmware via the NETGEAR recommended Mac app but it didn't go through, failing with a very cryptic error 103. I then used these instructions to do the transfer using the Terminal and it went through flawlessly in 18 seconds. I hope my experience is of help to others. I am back now on stock NETGEAR firmware, ready to upgrade to Voxel's again. Of course, I will not be doing a factory reset after the upgrade! The bricking of my Orbi has taken this discussion on a sidetrack so, coming back to the OP, my thought process now is to use Voxel's firmware to separate the 2.4GHz and 5GHz SSIDs so as to stop the interference between 5GHz network and my soundbar. Although Voxel himself cautions against separating the SSIDs, users who have done so seem to be very happy and I haven't seen any complaints. I now plan to not lower the power on the 5GHz network but to hide it and have my devices connect to the 2.4GHz one instead. That way, I can manually connect to the 5GHz network when needed (when I am not near my soundbar and need to transfer files for example) without it popping up on the list of networks and confusing other users. I am also unchecking "Enable 20/40 mhz coexistence" as there are no neighbours in the vicinity and this way I can use faster 2.4GHz networks without inconveniencing others. As my Internet speed is far lower than the speeds I get over a 2.4GHz network, I hope that this setup will enable me to get the benefits of a mesh network (seamless connectivity over a large area) while simultaneously using my Sony HT-ST5000 soudbar. I will report back after testing out my new setup 🤞.

After you disable the 5G SSID broadcast and applt the setting, make sure you remove all prior wifi profiles and or "forget this network" option on mobile devices. Once you do this, disable the wifi radio on the devices for 10 seconds then back ON. Then reconnect to the Orbi network, your devices will be connected to the 2.4Ghz SSID.

I did do that, as mentioned in the OP. Interestingly, I have noticed that after deleting the network information on the Mac it initially connects over the 2.4GHz network and then switches back to the 5GHz one after a few minutes. Also, I am curtious as to why the 5GHz network on channel 36, as seen on the WiFi explorer app, is being broadcast at all.

The signal is there however the SSID is just hidden. Do your mobile devices remain connected to the 2.4Ghz after you forget that nework and connect again? What happens if you disable the 5G SSID and turn down the Power to 25% and walk farther away from the RBR. Mobile devices should remain connected to the 2.4Ghz radio. The disabling of the 5Ghz SSID broadcast is only a short term solution for getting 2.4Ghz IoTs connected...Possible that the Mac still has some cached wifi information is maybe using the 2.4Ghz SSID name and password and trying to apply it to the 5Ghz signal and is getting connected, even though the SSID name is hidden.

Keep connecting to 5GHz network despite disabling 5GHz SSID broadcast

12 Replies

FURRYe38
Guru - Experienced User
Apr 26, 2020
After you disable the 5G SSID broadcast and applt the setting, make sure you remove all prior wifi profiles and or "forget this network" option on mobile devices. Once you do this, disable the wifi radio on the devices for 10 seconds then back ON. Then reconnect to the Orbi network, your devices will be connected to the 2.4Ghz SSID.
- Anjadekar
  Tutor
  Apr 26, 2020
  I did do that, as mentioned in the OP. Interestingly, I have noticed that after deleting the network information on the Mac it initially connects over the 2.4GHz network and then switches back to the 5GHz one after a few minutes.
  
  Also, I am curtious as to why the 5GHz network on channel 36, as seen on the WiFi explorer app, is being broadcast at all.
  - FURRYe38
    Guru - Experienced User
    Apr 26, 2020
    The signal is there however the SSID is just hidden.
    Do your mobile devices remain connected to the 2.4Ghz after you forget that nework and connect again?
    
    What happens if you disable the 5G SSID and turn down the Power to 25% and walk farther away from the RBR. Mobile devices should remain connected to the 2.4Ghz radio.
    
    The disabling of the 5Ghz SSID broadcast is only a short term solution for getting 2.4Ghz IoTs connected...Possible that the Mac still has some cached wifi information is maybe using the 2.4Ghz SSID name and password and trying to apply it to the 5Ghz signal and is getting connected, even though the SSID name is hidden.
Anjadekar
Tutor
Apr 27, 2020
Thank you all for weighing in on this. I am not trying to get connect to a 2.4 GHz signal to get IoT devices working but because the 5 GHz network interferes with my soundbar. CrimpOn, I feel much better knowing that my system is behaving "normally"!

After doing some further research I tried to upgrade to Voxel's firmware, which has an excellent reputation. I was able to successfully upgrade however, and very stupidly in hindsight, I tried to reset my Orbi after. This resulted in bricking the Orbi and I have spent the whole day trying to TFTP reset it with no success.

I am using a Mac and have tried everything from the NETGEAR recommended method of using the app to doing the reset via Terminal and then other options in a throw the kitchen sink approach. However, nada. Nothing. Zilch. I am not even able to ping the router.
The most promising lead I got were Hammerfest's posts (specifically posts #10 and #12) over at SNB Forums. He too went crazy getting the Orbi to go into TFTP but eventually succeeded. As per his suggestion I tried powering on the unit with the reset button pressed and after about 20 seconds or so got the amber light to keep blinking for a good few minutes. However, this didn't allow me to ping the router or get the TFTP process to work :-/

FYI, I was on stock firmware v2.5.1.16 before I upgraded to Voxel's firmware v9.2.5.1.17SF-HW. Also, would you guys know if the router is supposed to be at 192.168.1.1 or at 10.0.0.1? I have, of course, tried both (with the corresponding changes to my Mac's static IP) but with no luck.

I would hate to have to throw my Orbi away and would be extremely grateful to you guys if you can help me get it back to life!

PS - I would love to post about this over at SNB too but it looks like new users are not allowed to post :-/
- FURRYe38
  Guru - Experienced User
  Apr 27, 2020
  SNB forums you can post at any time even after you become a new member. IF there is a problem, please contact the forum moderator there. I've not experienced a problem of resetting the RBR after Voxels FW was loaded. However I see that this seems to be a problems with Voxel most recent FW version. I haven't updated to this version. :smileyfrustrated:
  
  Do you have access to a Windows PC or laptop? Friend, Neighbor or Famiy member? I would get on to a windows PC to check this.
  
  Anjadekar wrote:
  Thank you all for weighing in on this. I am not trying to get connect to a 2.4 GHz signal to get IoT devices working but because the 5 GHz network interferes with my soundbar. I feel much better knowing that my system is behaving "normally"!
  
  After doing some further research I tried to upgrade to Voxel's firmware, which has an excellent reputation. I was able to successfully upgrade however, and very stupidly in hindsight, I tried to reset my Orbi after. This resulted in bricking the Orbi and I have spent the whole day trying to TFTP reset it with no success.
  
  I am using a Mac and have tried everything from the NETGEAR recommended method of using the app to doing the reset via Terminal and then other options in a throw the kitchen sink approach. However, nada. Nothing. Zilch. I am not even able to ping the router.
  The most promising lead I got were Hammerfest's posts (specifically posts #10 and #12) over at SNB Forums. He too went crazy getting the Orbi to go into TFTP but eventually succeeded. As per his suggestion I tried powering on the unit with the reset button pressed and after about 20 seconds or so got the amber light to keep blinking for a good few minutes. However, this didn't allow me to ping the router or get the TFTP process to work :-/
  
  FYI, I was on stock firmware v2.5.1.16 before I upgraded to Voxel's firmware v9.2.5.1.17SF-HW. Also, would you guys know if the router is supposed to be at 192.168.1.1 or at 10.0.0.1? I have, of course, tried both (with the corresponding changes to my Mac's static IP) but with no luck.
  
  I would hate to have to throw my Orbi away and would be extremely grateful to you guys if you can help me get it back to life!
  
  PS - I would love to post about this over at SNB too but it looks like new users are not allowed to post :-/
Anjadekar
Tutor
Apr 27, 2020
I have some great news! I was able to unbrick my Orbi!

I used this excellent tip to keep the Mac plugged into the router and then restart it with the reset button pushed down with a paperclip. As soon as the router started and the red light blinked I pinged 192.168.1.1 (while keeping the reset button pushed down) from Terminal and, voila, the red light kept flashing and TFTP mode was activated! I then took the pin out of the reset button and initiated the transfer of the firmware via the NETGEAR recommended Mac app but it didn't go through, failing with a very cryptic error 103. I then used these instructions to do the transfer using the Terminal and it went through flawlessly in 18 seconds. I hope my experience is of help to others.

I am back now on stock NETGEAR firmware, ready to upgrade to Voxel's again. Of course, I will not be doing a factory reset after the upgrade!

The bricking of my Orbi has taken this discussion on a sidetrack so, coming back to the OP, my thought process now is to use Voxel's firmware to separate the 2.4GHz and 5GHz SSIDs so as to stop the interference between 5GHz network and my soundbar. Although Voxel himself cautions against separating the SSIDs, users who have done so seem to be very happy and I haven't seen any complaints. I now plan to not lower the power on the 5GHz network but to hide it and have my devices connect to the 2.4GHz one instead. That way, I can manually connect to the 5GHz network when needed (when I am not near my soundbar and need to transfer files for example) without it popping up on the list of networks and confusing other users. I am also unchecking "Enable 20/40 mhz coexistence" as there are no neighbours in the vicinity and this way I can use faster 2.4GHz networks without inconveniencing others.

As my Internet speed is far lower than the speeds I get over a 2.4GHz network, I hope that this setup will enable me to get the benefits of a mesh network (seamless connectivity over a large area) while simultaneously using my Sony HT-ST5000 soudbar. I will report back after testing out my new setup 🤞.
- FURRYe38
  Guru - Experienced User
  Apr 27, 2020
  Glad the system is back up and running. Let us know how it goes...
  
  Anjadekar wrote:
  I have some great news! I was able to unbrick my Orbi!
  
  I used this excellent tip to keep the Mac plugged into the router and then restart it with the reset button pushed down with a paperclip. As soon as the router started and the red light blinked I pinged 192.168.1.1 (while keeping the reset button pushed down) from Terminal and, voila, the red light kept flashing and TFTP mode was activated! I then took the pin out of the reset button and initiated the transfer of the firmware via the NETGEAR recommended Mac app but it didn't go through, failing with a very cryptic error 103. I then used these instructions to do the transfer using the Terminal and it went through flawlessly in 18 seconds. I hope my experience is of help to others.
  
  I am back now on stock NETGEAR firmware, ready to upgrade to Voxel's again. Of course, I will not be doing a factory reset after the upgrade!
  
  The bricking of my Orbi has taken this discussion on a sidetrack so, coming back to the OP, my thought process now is to use Voxel's firmware to separate the 2.4GHz and 5GHz SSIDs so as to stop the interference between 5GHz network and my soundbar. Although Voxel himself cautions against separating the SSIDs, users who have done so seem to be very happy and I haven't seen any complaints. I now plan to not lower the power on the 5GHz network but to hide it and have my devices connect to the 2.4GHz one instead. That way, I can manually connect to the 5GHz network when needed (when I am not near my soundbar and need to transfer files for example) without it popping up on the list of networks and confusing other users. I am also unchecking "Enable 20/40 mhz coexistence" as there are no neighbours in the vicinity and this way I can use faster 2.4GHz networks without inconveniencing others.
  
  As my Internet speed is far lower than the speeds I get over a 2.4GHz network, I hope that this setup will enable me to get the benefits of a mesh network (seamless connectivity over a large area) while simultaneously using my Sony HT-ST5000 soudbar. I will report back after testing out my new setup 🤞.
randomousity
Luminary
Apr 27, 2020
I don't have any Apple products, so take this with a grain of salt, but you may be able to block your computers (and maybe phones) from connecting to certain wireless networks via MAC addresses. The router and satellite should each have a unique MAC address for 5GHz and 2.4GHz (plus one for each ethernet LAN or WAN interface). So, for instance, the RBR50 should have like seven MAC addresses: 1x ethernet WAN, 3x ethernet LAN, 3x WiFi (since it's triband; 1x 2.4GHz, and 2x 5GHz (one for devices, and one for the backhaul to your satellite(s)). The RBS50 should be basically the same, except 0x ethernet WAN interfaces, and 4x ethernet LAN interfaces.

You may be able to go into your network settings on your computer and basically blacklist the router's and/or satellite's 5GHz MAC address(es), which should then force it to connect only to the 2.4GHz radio instead. This is probably easier to do on a computer than a phone, and may be impossible to do on any smart IoT devices you can't operate on directly (e.g., smart speakers, wireless speakers, etc., that require configuration through an app or website). But, in theory, any device with advanced network configuration settings where you can block APs should allow you to force it to connect to one radio or the other by blocking the one you don't want it to use, thus forcing it to use the other.

You'll have to figure out the MAC addresses for the router and satellite(s) for the bands you want to block, and figure out how to configure each device you want to specify the band it uses.

Forum Discussion

Keep connecting to 5GHz network despite disabling 5GHz SSID broadcast