NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 is not supporting 900Mb+- on the WAN to LAN test
So I'd like to call NG's attention to the following test results for Orbi RBR50. I'm not seeing anything near 900mbps on the WAN to LAN test. Using both iPerf and Duckwares simple WAN to LAN test pro...
Ok, so after loading v38 on my RBR50 from last week no big issues there. Today I wanted to re-test for WAN to LAN speeds with v38 loaded.
Though better results from my initial test from prior FW version, still not seeing anything near 900Mbps after a factory reset and simple setup:
BPS=499,384,824
0: 62,220,337 (497,762,696 bps)
1: 64,979,116 (519,832,928 bps)
2: 64,417,581 (515,340,648 bps)
3: 63,067,730 (504,541,840 bps)
4: 65,513,878 (524,111,024 bps)
5: 60,189,054 (481,512,432 bps)
6: 62,540,081 (500,320,648 bps)
7: 65,600,714 (524,805,712 bps)
8: 64,502,549 (516,020,392 bps)
9: 62,906,779 (503,254,232 bps)
10: 57,804,877 (462,439,016 bps)
11: 54,562,161 (436,497,288 bps)
12: 62,602,220 (500,817,760 bps)
13: 63,736,316 (509,890,528 bps)
14: 64,919,285 (519,354,280 bps)
15: 58,105,313 (464,842,504 bps)
16: 58,896,232 (471,169,856 bps)
17: 64,852,544 (518,820,352 bps)
18: 62,907,253 (503,258,024 bps)
19: 63,936,806 (511,494,448 bps)
500Mbps seems to be the average for my unit. I presume this may still effect some others as well. Not sure what is the root cause. The RBR needs HW NAT accelleration to achieve the higher 900Mbps speeds.
My RBR850 sees 900Mbps using same test methods:
BPS=948,864,032
0: 118,388,264 (947,106,112 bps)
1: 118,656,612 (949,252,896 bps)
2: 118,645,652 (949,165,216 bps)
3: 118,493,080 (947,944,640 bps)
4: 118,640,768 (949,126,144 bps)
5: 118,648,578 (949,188,624 bps)
6: 118,499,186 (947,993,488 bps)
7: 118,612,055 (948,896,440 bps)
8: 118,591,977 (948,735,816 bps)
9: 118,662,758 (949,302,064 bps)
10: 118,484,783 (947,878,264 bps)
11: 118,628,460 (949,027,680 bps)
12: 118,661,544 (949,292,352 bps)
13: 118,497,743 (947,981,944 bps)
14: 118,655,652 (949,245,216 bps)
15: 118,612,888 (948,903,104 bps)
16: 118,644,823 (949,158,584 bps)
17: 118,634,157 (949,073,256 bps)
18: 118,630,705 (949,045,640 bps)
19: 118,642,596 (949,140,768 bps)
I have the same problem: https://community.netgear.com/t5/Orbi/Lower-speed-than-contracted-from-the-router-to-the-computer/m-p/1818027/highlight/true#M74304
I think the problem is that the QoS is enabled by default and cannot be disabled.
It's embarrassing that a product like this has this flaw. :smileymad:
Interesting assumption. Hadn't thought about that. I know from other NG routers I test, I see near 900Mbps on them. The RBR50 seems to be the only one that doesn't. Even after a factory reset I can't get it to 900Mpbs.
j1simon wrote:I have the same problem: https://community.netgear.com/t5/Orbi/Lower-speed-than-contracted-from-the-router-to-the-computer/m-p/1818027/highlight/true#M74304
I think the problem is that the QoS is enabled by default and cannot be disabled.
It's embarrassing that a product like this has this flaw. :smileymad:
I assume it is the QoS of the router because the speed tests always approach 50% of the speed detected by the RBR50 in its Speed Test (in router webUI > Advanced > Setup > Speed Test). I attach a screenshot.
Whether I test it from my computer connected by LAN cable to RBR50 or from my devices connected by wifi.
On the other hand a search for RBR50 + QoS on Google shows many results about this.
Ya we saw this before where users mentioned that if a factory reset was performed, and if QoS, Traffic Meter and Access Controls were not touched, Speeds would be near 900Mpbs. I don't touch these in my testng for this. I presume something has happened in FW that seems to suggest that QoS on the WAN to LAN side is slowing things down even after a factory reset.
I would make contact with NG support about this. I have mentioned this to forum moderators. Haven't hear back anything since my initial post about this. They said they would get engineering looking into this. The more nagging we do, maybe this will get fixed. :smileywink:
