I have the Costco product with 1 router (RBR50) and 2 satellites (RBS50). One satellite is stable, while the other intermittently drops. I recently looked at the router logs and saw that the problem sat (:dd) is constantly doing DHCP. Does that mean something? Notice that the stable sat (:1c) hardly requests DHCP. The [snip] represents the part of the MAC address I've redacted because I felt like it -- don't judge me.
Does this seem like a hardware problem or another case of firmware bugs?
[DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:42:39 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:42:37 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:05:13 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:05:12 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:04:39 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 15:04:38 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:49:34 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:49:31 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:48:59 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:48:59 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:45:44 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:45:43 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 14:44:55 [DHCP IP: 10.0.0.3] to MAC address [snip]:1c, Monday, November 27, 2017 13:10:05 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 13:09:58 [DHCP IP: 10.0.0.3] to MAC address [snip]:1c, Monday, November 27, 2017 08:23:11 [DHCP IP: 10.0.0.3] to MAC address [snip]:1c, Monday, November 27, 2017 08:23:10 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 08:23:10 [DHCP IP: 10.0.0.2] to MAC address [snip]:dd, Monday, November 27, 2017 08:23:09
Model: Orbi High-Performance AC3000 Tri-Band WiFi System (RBK50)
I have the RB33K, and one satellite is 37 feet away the other 39 feet. Everything is performing well. I had blue lights at the initial placement, with no satellite disconnect issues to date. I do not believe there is a generalization about close and far (other than Netgear saying 30 feet minimum, 70 feet maximum). Enviroment, interference, and obstacles play a huge role in affecting the 5GHz backhaul.
I have the RB33K, and one satellite is 37 feet away the other 39 feet. Everything is performing well. I had blue lights at the initial placement, with no satellite disconnect issues to date. I do not believe there is a generalization about close and far (other than Netgear saying 30 feet minimum, 70 feet maximum). Enviroment, interference, and obstacles play a huge role in affecting the 5GHz backhaul.
Absolutely interference plays a huge role for 5ghz. However, many people had the Orbi running for 6 months to a year with the pre 2.x firmware and had to move sats after the 2.x upgrade was released.
Bottom line is, the pre 1.10.x firmware was largely stable for everyone, but starting with the 1.10.x release, it went highly unstable for large groups of users randomly.
Interesting. The RBK33 package has the latest at 2.0.0.56 for the Router and 2.0.0.34 for the satellites. That was a major firmware jump for the units I bought and I had no issue. As you say there are random variables happening.
Interesting. The RBK33 package has the latest at 2.0.0.56 for the Router and 2.0.0.34 for the satellites. That was a major firmware jump for the units I bought and I had no issue. As you say there are random variables happening.
Most I've seen with the stability problems are those with the 50's, not the slower units. For instance, I had the 50 plus two sats beginning in March. Perfectly stable, no disconnects, over 90 devices. Beginning with the 1.10.x firmware, I have periods of erratic connects and stability. For instance, last night, using FINGBOX, I can see one sat connected and reconnected every 5 minutes for 4 hours. Several days ago, it was fine.
Interesting. The RBK33 package has the latest at 2.0.0.56 for the Router and 2.0.0.34 for the satellites. That was a major firmware jump for the units I bought and I had no issue. As you say there are random variables happening.
Most I've seen with the stability problems are those with the 50's, not the slower units. For instance, I had the 50 plus two sats beginning in March. Perfectly stable, no disconnects, over 90 devices. Beginning with the 1.10.x firmware, I have periods of erratic connects and stability. For instance, last night, using FINGBOX, I can see one sat connected and reconnected every 5 minutes for 4 hours. Several days ago, it was fine.
One thing I did notice is that when I set up I had a hub and spoke connection, and after the firmware update, which allows daisy chaining, it kept the hub and spoke as optimal (I assume optimal). The daisy chaining option could enter into a connection probllem relative to placement and varying conditions.
Interesting. The RBK33 package has the latest at 2.0.0.56 for the Router and 2.0.0.34 for the satellites. That was a major firmware jump for the units I bought and I had no issue. As you say there are random variables happening.
Most I've seen with the stability problems are those with the 50's, not the slower units. For instance, I had the 50 plus two sats beginning in March. Perfectly stable, no disconnects, over 90 devices. Beginning with the 1.10.x firmware, I have periods of erratic connects and stability. For instance, last night, using FINGBOX, I can see one sat connected and reconnected every 5 minutes for 4 hours. Several days ago, it was fine.
One thing I did notice is that when I set up I had a hub and spoke connection, and after the firmware update, which allows daisy chaining, it kept the hub and spoke as optimal (I assume optimal). The daisy chaining option could enter into a connection probllem relative to placement and varying conditions.
Yes, 2.0.x introduced daisy channing. However, in my case, I remain in a star topology.
