R3 connecting to higher ping servers vs XR500

[skschatzman]

I've been messing with the R3 for many hours now. Updated the firmware and factory reset afterwards. I have it set up exactly how my XR500 is.

On my XR500 I connect to 20ms MW3 servers all day.

My R3 only ever connects to 35-49ms servers. This is with or without the geofilter enabled.🤷‍♂️

[Netduma Fraser]

his will most likely be caused by Steady Ping on the Geo-Filter. Essentially a ping buffer is added to your ping that absorbs any spiking/instability from the game ping that you normally would have felt. The result is a consistent ping throughout the entire game allowing for a smoother experience. You can disable this by clicking Steady Ping at the top of the Geo-Filter map. You can also experiment with the buffer amount.

[DARKNESS]

@skschatzmanDisable Geo-latency and you should see servers connect to lower ping servers however there is steady ping which might be the cause depending on how you set it up as fraser said

[skschatzman]

1 hour ago, Netduma Fraser said:

his will most likely be caused by Steady Ping on the Geo-Filter. Essentially a ping buffer is added to your ping that absorbs any spiking/instability from the game ping that you normally would have felt. The result is a consistent ping throughout the entire game allowing for a smoother experience. You can disable this by clicking Steady Ping at the top of the Geo-Filter map. You can also experiment with the buffer amount.

Isn't steady ping tied to the geo-filter?

When I disable geo-filter, I still have higher ping.

Is there a way to disable steady ping so I can test it?

[Netduma Fraser]

Yes it is though it's not filtering, so you'd have to disable it separately which can be done by clicking Steady Ping at the top of the map

[skschatzman]

On 12/19/2023 at 2:16 PM, Netduma Fraser said:

Yes it is though it's not filtering, so you'd have to disable it separately which can be done by clicking Steady Ping at the top of the map

Ok so I've played over 8 hours of MW3 since I disabled steady ping. Out of that 8 hours I have only connected to a single game that was 19-21ms. A majority of the games were 25-30ms and a few 35-40ms.

This is with geo-filter on or off. I did half on half off.

I then plug my XR500 back in with the same geo-filter settings and immediately get into 19-21ms lobbies. Over the next couple hours roughly 3 out of every 4 games is on a 19-21ms server. The 1 out of 4 games were on 25-30ms.

So there is the issues of connecting to higher ping servers and the steady ping is artificially inflating the ping by a large amount vs consistent gaming results of my XR500.

I had high expectations because it is a 100% software and hardware Netduma router. With all the trouble the XR500 was getting it to where it is now, I figured the R3 would be a clear upgrade.

I really like the new look and snappy feel of the R3 menu navigation, but consistent gaming performance is(was?) the main point of your business model.

Like the XR500, was the R3 half baked and we are expected to beta test it over the next few years before the results are equally or more consistent?

🤷‍♂️

[Netduma Fraser]

I've sent you a firmware which may help with this, please let us know.

We're releasing a video on Steady Ping on our YT channel in about 25minutes which will help explain why it does that

[x12Tyler]

I understand what steady ping is doing but like him I believe the issue is even when disabling steady ping the base ping of games is going higher for some reason. As an example the Georgia server for me has always been 14-16ms max but on the r3 although will still briefly ping that low if you run multiple tests on the ping heatmap instead is staying around 18-2 on the heatmap and in game. Hooked my r2 up just to make sure it wasn’t something with the game and instantly every game 14-16ms again instead of 18-21

[Rvmbo]

On 12/22/2023 at 12:34 PM, Netduma Fraser said:

I've sent you a firmware which may help with this, please let us know.

We're releasing a video on Steady Ping on our YT channel in about 25minutes which will help explain why it does that

I am having the same issue that was expressed earlier in the forum. On my xr1000 i get servers in NJ and PHL with 18-22 pings which i am use to but now with the netduma r3 i am getting 30+ on my server closet to me? i have optimized ping, geo enabled and steady ping enabled? I dont get it, is there something im doing wrong or should i go back to using my xr1000 until future updates get pushed out for the Netduma R3 

[Netduma Fraser]

7 hours ago, x12Tyler said:

I understand what steady ping is doing but like him I believe the issue is even when disabling steady ping the base ping of games is going higher for some reason. As an example the Georgia server for me has always been 14-16ms max but on the r3 although will still briefly ping that low if you run multiple tests on the ping heatmap instead is staying around 18-2 on the heatmap and in game. Hooked my r2 up just to make sure it wasn’t something with the game and instantly every game 14-16ms again instead of 18-21

6 hours ago, Rvmbo said:

I am having the same issue that was expressed earlier in the forum. On my xr1000 i get servers in NJ and PHL with 18-22 pings which i am use to but now with the netduma r3 i am getting 30+ on my server closet to me? i have optimized ping, geo enabled and steady ping enabled? I dont get it, is there something im doing wrong or should i go back to using my xr1000 until future updates get pushed out for the Netduma R3 

Possibly it could be just introducing a new router into your setup, some ISPs seem to take a little while to get settled when there is a new router. A good test would be to take the MAC address of your previous router and make the R3 use that instead. As well as dialing in your Congestion Control/SmartBOOST settings. If you're using WiFi instead of ethernet experiment with the channels/widths to find what works best for you. 

I've also provided a firmware via PM that may improve things.

[skschatzman]

On 12/24/2023 at 12:44 AM, x12Tyler said:

 

 

On 12/24/2023 at 8:37 AM, Netduma Fraser said:

Possibly it could be just introducing a new router into your setup, some ISPs seem to take a little while to get settled when there is a new router. A good test would be to take the MAC address of your previous router and make the R3 use that instead. As well as dialing in your Congestion Control/SmartBOOST settings. If you're using WiFi instead of ethernet experiment with the channels/widths to find what works best for you. 

I've also provided a firmware via PM that may improve things.

Just like what Tyler said. My router has been up for nearly a week now with that firmware you shared. It seems to be stable, but the base ping is about +5-10ms (vs the XR500) with all the bells and whistles disabled on a hardwired connection.

I understand that new hardware can take some time to stabilize but I can literally swap out the routers and within minutes have consistently faster connections on my XR500. 

I can't believe I'm saying this, but it seems like the R3 isn't as efficient as my XR500. New features are great, but I would expect the base performance to at least be on par with your previous generation equipment. Is this something you guys are actively looking into?

Edit: I just saw another thread for this issue. I'll just migrate my issue there.

[Netduma Fraser]

9 hours ago, skschatzman said:

 

Just like what Tyler said. My router has been up for nearly a week now with that firmware you shared. It seems to be stable, but the base ping is about +5-10ms (vs the XR500) with all the bells and whistles disabled on a hardwired connection.

I understand that new hardware can take some time to stabilize but I can literally swap out the routers and within minutes have consistently faster connections on my XR500. 

I can't believe I'm saying this, but it seems like the R3 isn't as efficient as my XR500. New features are great, but I would expect the base performance to at least be on par with your previous generation equipment. Is this something you guys are actively looking into?

Edit: I just saw another thread for this issue. I'll just migrate my issue there.

In that case, please do the following, ideally testing with PingPlotter and offering a plot from your ISP modem as a comparison:

1. Ensure the upstream/ISP modem/router the R3 is connected to is setup with the R3 in its DMZ or in modem/bridge mode.
2. Ensure ALL devices are connected to the R3 or at the very least that there are no devices connected/using internet on the upstream router when testing
3. If you have multiple ethernet cables test using different cables connecting the R3 to the modem/the R3 to your device
4. Disable IPv6 in LAN/WAN
5. Please state if you are using PPPoE, VLAN or DHCP identifiers
6. Use a different DNS such as 1.1.1.1 / 1.0.0.1
7. As a test make an Internet rule to the device and allow ALL traffic then test, is there a difference? (Settings > Internet Rules)
8. As a test put the PC in the DMZ (briefly for the test then remove), then do a test, is there a difference?
9. Remove all prioritizations from SmartBOOST including activities/devices
10. If the above doesn't help disable SmartBOOST entirely from the 3 dots menu top right of the page  > Settings then test
11. Disable Steady Ping on the Geo-Filter page in case it is affecting traffic outside the Geo-Filter - also ensure no devices are added there
12. Disable Adblocker
13. Ensure you have your correct speeds entered in Speed Test > Advanced
14. With SmartBOOST enabled, adjust Congestion Control in Ping Optimizer > Advanced and have it set to Always On and ensure speed test bypass is disabled
15. Ensure you're doing this test over a wired connection - NOT WiFi
16. Ensure in WAN/LAN Settings that the speeds of the ports are at 1Gbps
17. Remove any port forwarding/DMZ/static routes you may have set
18. Test at different times of the day i.e. during peak time (results may be worse) and during non peak times (should be better)

Once you've covered everything on this list please let us know the results. This should give us a good indicator of what the problem may be if it's covered in the list or whether it's something more on the backend. The team can then have a look.