NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OzGobo
Aug 12, 2023Aspirant
RBK50 Speed Tests don't match wired device throughput
Attached is an image of my Orbi Speedtest taken seconds before the same test on a Mac that is wired into the back of the RBK50. Should I expect these to be in the same ballpark? They are WAY off. I'm also only getting what the Orbi is reporting on wifi devices around the network, not what the wired device is getting. Would that setting or issue be impacting the wifi performance?
Normal? Ideas?
Internet Co-axial 1000MB direct to street cable (not to an internal building concentrator or anything)
RBK50 FW 2.7.3.22
RBS50 Wired Backhaul (x2) on different floors.
the Mac that was used to generate the screenshot is wired into he RBK50.
.
OzGobo wrote:
The Orbi is reporting 437 down, the macOS app on the device that is wired into it is reporting 893. This seems odd.🙂
Odd is correct. One would expect that the router itself and a device wired directly to the router would report the same speed. With a gigabit ISP connection, that is normally in the 800-900Mbps range. It is a bit irritating that the router Speed Test function does not report which Speed Test server was used to perform the test. (Notice that the Mac reported using Verizon and offers an option to select a different server.) In my case, I have noticed that Speed Test reports can vary significantly.
It might be worth running Speed Test on the Orbi several times to see if the reports are consistent over time.
WiFi device speed is definitely a function of the WiFi network and specific device capabilities. The RBK50 ("K" for "Kit", consisting of one RBR50 Router ("R") and one or more RBS50 Satellites ("S") is built on 802.11ac technology with two antennas (2x2 MIMO). A WiFi device with two antennas can theoretically achieve a Link Rate of 867Mbps when placed very close to an access point. Internet searches for "what speed can I expect to get?" turn up all sorts of information.
I do not find it surprising that WiFi devices connected to this 802.11ac system continue to report Speed Tests in the 400Mbps range even with the higher ISP connection.
p.s. On the matter of firmware. I am pretty confident that updating the firmware will have little or no impact on this specific issue. I, myself, updated to the current V2.7.5.4 in the spring and have found nothing amiss.
6 Replies
Sort By
OzGobo wrote:
Attached is an image of my Orbi Speedtest taken seconds before the same test on a Mac that is wired into the back of the RBK50.
The speedtest on the app measures the throughout between the router and the modem. In other words, while it uses wifi, that is just to control the test. It effectively measures the speed of your internet connection.
Anything else has to navigate whatever else is on your network.
Your wifi speeds will never match your wired speeds. They depend on the technology on your wifi clients.
If your ethernet wired Mac has the same speeds as your wifi clients, then something odd is happening.
Are you deliberately ignoring the advice to get new firmware for your router?
- OzGoboAspirant
Hi there,
Thanks for the reply.
>>The speedtest on the app measures the throughout between the router and the modem.
Perhaps I'm not understanding you. That webpage from the Orbi is loaded on the wired Mac, as is the app. its a screenshot from the same device. The Orbi is reporting 437 down, the macOS app on the device that is wired into it is reporting 893. This seems odd. The only reason I'm concerned is that wireless devices don't seem to get above about 420 anywhere on my network, and I'm wondering if this test result is any in anyway impacting that performance. I don't expect to get 893 from a wired device on this network, but I'm thinking with 890+ coming in the front door it could potentially be better for the wireless devices?
As a bit of history, the speed of the internet connection was recently increased from 250MBPS to 1000. While it was set at 250, the Orbi app consistently reported 256MBSP down, and 24 Up. Supposedly its now 1000 down and 50 up. Since that, all Orbi devices have been restarted, as have many of the devices in the network. Both backhauls are ethernet.
>>Are you deliberately ignoring the advice to get new firmware for your router?
The fam-bam do not like me taking down the connection to install new firmware, and being old I spend a lot more time in bed than they do. Not so much ignoring it, as just old and sleepy at the times I could do it without risking someone hacking off a limb 🙂
.
OzGobo wrote:
The Orbi is reporting 437 down, the macOS app on the device that is wired into it is reporting 893. This seems odd.🙂
Odd is correct. One would expect that the router itself and a device wired directly to the router would report the same speed. With a gigabit ISP connection, that is normally in the 800-900Mbps range. It is a bit irritating that the router Speed Test function does not report which Speed Test server was used to perform the test. (Notice that the Mac reported using Verizon and offers an option to select a different server.) In my case, I have noticed that Speed Test reports can vary significantly.
It might be worth running Speed Test on the Orbi several times to see if the reports are consistent over time.
WiFi device speed is definitely a function of the WiFi network and specific device capabilities. The RBK50 ("K" for "Kit", consisting of one RBR50 Router ("R") and one or more RBS50 Satellites ("S") is built on 802.11ac technology with two antennas (2x2 MIMO). A WiFi device with two antennas can theoretically achieve a Link Rate of 867Mbps when placed very close to an access point. Internet searches for "what speed can I expect to get?" turn up all sorts of information.
I do not find it surprising that WiFi devices connected to this 802.11ac system continue to report Speed Tests in the 400Mbps range even with the higher ISP connection.
p.s. On the matter of firmware. I am pretty confident that updating the firmware will have little or no impact on this specific issue. I, myself, updated to the current V2.7.5.4 in the spring and have found nothing amiss.