NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Miklosman
Mar 09, 2020Aspirant
RBR50 with RBS50 - WiFi camera connect to distant router
Cameras and all HomeKit devices connect to a far away RBR50 o RBS50. In consequence not working well because having a low WiFi signal. Is there a way to fix some devices only to some satellites RBS50 ...
tomschmidt
Mar 12, 2020Virtuoso
I made some time to experiment a bit. I normally have Implicit Beamforming and Fast Roaming both enabled. Disabling Beamforming did not help, nor did disabling Fast Roaming, nor disability both. I also tried reducing the power level of the 2.4GHz signal, but even at 50% power the IoT device would use the radio from the router (furthest away) even though two satellites are closer with stronger signals. Once reduced to 25% power, the IoT device did connect to the satellite since the router's 2.4GHz signal was to weak, however then all my 2.4GHz devices on the other end of the house where the router is lost complete connectivity.
Conclusion: Implicit Beamforming nor Fast Roaming affect the race condition of IoT devices binding to the router before any satellites (provided the routers signal is strong enough). This race condition is due to the radio being turned on for the router before the satellites, thus clients bind to the first strong-enough radio signal they see.
I can understand that the 5GHz backhaul has to be enabled first. Once the backhaul is established, then the 2.4GHz and 5GHz client radios should be enabled simultaneously on the router and all satellites. I am wondering if NG is instead enabling the backhaul and all client radios on the router simultaneously, long before the satellites backhaul and client radio is working, thus causing this race condition.
FURRYe38
Mar 12, 2020Guru - Experienced User
Good explanation and info. I agree.