AsNCo

As mentioned in a previous post on this thread, my setup is,
Modem to (Wired) R3 to (Wired) Switches to (Wired) Asus AX11000 AP to (Wireless) 2nd AP.

Basically, multiple phones have the WhatsApp Voice Call issue as well. To solve it, just have to turn off Wi-Fi on the phone and turn it on again to ensure a stable internet connection.

Ok. The next time I encounter this, I'll try disconnecting the Ethernet from the R3 to the Asus AX11000 AP and reconnecting it again to see if Internet is restored that way.

Hi everyone,
The wait is over, we're happy to deliver the latest R3 firmware. It contains months of work from our development team, with a big focus on improving the stability and reliability of our features.
Main Changes:
Hybrid VPN is here: this is long standing Netduma feature which allows you to run your VPN through your router and then choose which devices or applications the VPN should be applied to. This means you can run your VPN on things that usually hard run a VPN on, such as Smart TVs and consoles. Hybrid VPN is compatible with OpenVPN and WireGuard, so make sure your VPN provider supports one of these protocols. Added UPnP Relay. Previously, if your R3 was connected underneath an ISP router, you'd likely see a Double NAT reported on your games console unless you did some manual port forwarding. UPnP Relay pushes port opening requests from your devices up the chain to your ISP router, meaning you should get an open NAT with no additional configuration needed Some users reported issues with Chromecast or Airplay, or transferring files locally. These are fully fixed now. Many quality of life / annoying bugs fixed, including improved IPv6 and PPPoE support, increasing the reliability of the Geo-Filter ping graph and increasing the reliability of the Ping Optimiser test (with further improvements to come) A longer changelog is below.
We want the Netduma R3 to be the best router in the world, and we're taking another step towards that goal with this firmware. We'll continue working on and releasing updates, so please give us any feedback you have.
 
INSTALL GUIDE
You can install the firmware using one-click update. Simply open up DumaOS and look for the green "Update Available" icon.
Alternatively, you can download the file below, then go to Settings > Troubleshooting > Upload Firmware, then upload the file.
DumaOS-R3-4.0.219.sig
NOTE: You need to login to the forum before you can download this file. If you don't want to make an account, use one-click update as described above.
 
Changelog:
Hybrid-VPN added Improved performance of SmartBOOST Improved performance of Steady Ping Improved performance of Geo-Filter Ping graph appears more frequently Ping Optimiser reliability improvements Chromecast/AirPlay compatibility fixed UPnP relay added (no more double NAT) Increased maximum speeds Improved compatibility with IPv6 and PPPoE Optimisations to improve memory usage Many other smaller bug fixes

Thr guy is a clown man should see his comments I read the forum everyday, in hopes of news of this thing actually working without hard resetting twice a day the stuff that he comes out with, #1 netduma brown noser.

It has been requested so it will likely come in future, I will ask the team to see if they can get it in the next one if it's a small job. 

My blind sister could drop a nuke in this lobby lol 

Great results on the new firmware with Bufferbloat. 62.5% UP/DOWN for Congestion Control for my 1000/1000 Fibre connection.
Wifi also seems marginally faster and more consistent.
Gaming I have yet to try, will update.

I had the same experience as you until I rebooted the router. Every time I reboot, there will 2 things that I'll need to change again because the settings doesn't stick.
They are, Disable Steady Ping and Disable Speedtest Bypass.

Now I redid the bufferbloat test. As for CC, I set it to Auto which in the Speed Settings, were set to (for my own ISP) 1Gbps up and down.

The difference in the bufferbloat test between 'Low Latency Only' and 'Auto' in CC Modes makes a big difference in the ping when download or upload is active. 'Auto' gives me very close speeds to 'Low Latency Only' while giving me very low ping.

So what I would recommend is to set it to 'Auto' and then reboot the router, and then Disable Speedtest Bypass & Steady Ping (if you so wish). Then redo your Bufferbloat test. The results should be a lot better. It is for me at least.

Perhaps you weren't aware of your snobbery shining through your posts. His has none of it. It was purely informative. Not to mention, he explains it well without resorting to belittling others who has different expectations than you. Wanting a sub 20ms ping = laughable? We've been having the mindset that Ping is King for years and then suddenly, there's the new idea that stability is what we should be aiming for at the expense of higher latency. Of course it takes time for others to grasp that. I'm not going to take such info at face value. I'm going to give it time to cook and see for myself.

8.8.8.8 and 1.1.1.1 are literally my primary and secondary DNSes too as what you'd also recommend. So yup.

As for why I need the boot-up time to be faster, I have a lot of Home Automation devices. They will start acting crazy and not be responsive if there has been a long enough delay without any internet. Simply restarting the modem, router and APs is not going to cut it. It will still act crazy. I'll have to physically go all around the house and manually turn off all of the Home Automation devices and then restart the router and APs first before turning on the Home Automation devices. Thus why, I love how fast my modem and R2 starts up. Both are up and running in under 20s. And because Ethernet gets the internet 1st in those 20 seconds, the APs are already there to make sure the Home Automation devices did not experience any internet downtime in those few short seconds.
The reason why I have to keep rebooting the R2 every week or so is because of the random internet disconnects (not WiFi) causing problems for not just my Home Automation but also me and my family's phones where the only way to make sure the internet on the apps will load is by turning the WiFi off and on again. Hope that explains why I am particular about the boot time and the annoyance especially when you have this many Home Automation devices which are as finicky as they are.
Like how even Alexa will randomly still be in listening mode when you've finished speaking to her and she's stuck there with the circle processing for quite a long time and then turning off like as if no one spoke. And you'll have to repeat again and then she'll suddenly execute the command twice in the process. Notice that that is an issue with the R2. Similarly with the XR500. Suspect it to be a DHCP issue. And yes, I've even allocated manual IP addresses to them. But hope this addresses my concern on the extremely slow boot-up time. PS, I've also suddenly randomly lost internet and my access to the R3. Even though the R3 was still up and running. Not just my wired desktop, but my other devices lost internet too. Resulting in me having to reboot the router. So that's another reason why I would need to reboot the R3 once in a while too.

In the meantime, when I'm not gaming, which is what I mostly do since I don't have ample time to game anymore, I aim to make full use of my internet speed that I paid for. So is it wrong for me to not want my full bandwidth and low latency that my ISP offers?

Again, if I wanted to jump on the hate bandwagon, the answer is simple. Don't buy and support the product. It's that simple. I've dropped COD for years for that very reason. The lag compensation being one of factors turning me off to it. Overwatch on the other hand feels a lot more responsive at low ping. Playing on servers outside my country, 60ms or more, I can easily experience lag. Thus my desire to keep it low since the servers are literally a few km away. But again, the ability to take advantage of lag compensation can also be great. Thus, I see the benefits to having a router that has this feature that can be used in years to come even if I can't take full advantage of it now.

As for the hate bandwagon again, if I really wanted to bash it, I wouldn't have bought the R1, XR500, R2 and now the R3. I've been happy with the R2 despite there being a few issues. But I didn't bring it up for months as I'm overall, really satisfied with it. I noticed a few problems with the R3, some, were slightly worst than the R2 and thus, I wanted to bring any and all issues that I noticed in the hopes that there can be improvements made or fixes for it. It's as simple as that. There's no hate here. Just wanting my favourite product to be better. But then again, you started not acknowledging my issues and saying that they don't matter. How would that feel to someone?
If I'm wrong educate me. Don't belittle me in the process.

Everyone connection will be different when it comes to Congestion Control settings. There are various possible reasons as to why, but in the end. It all narrows down to, plainly, how your ISP handles your connection.

Now, with that said, Ping Optimizer will try to establish your connection from not having HUGE ping spikes when your connection is saturated with many devices. So it will give you a baseline result in being able to maintain numerous devices and still be able to game.
Now, the beauty with DumaOS, is the ability to utilize many tools that are packed into DumaOS. SmartQOS is just one of them to be able to 'automatically' do it for you.
Ping Optimizer having the option 'Advanced' is exactly for those wanting to 'FINE TUNE' their settings to get it right for their network/gaming environment.
I don't have asymmetrical gigabit, so I can utilize Ping Optimizers 'Advanced' settings and fine tune my settings to say half. So, instead of me using 950d/40u down, I just enter my speeds manually to 500d/20u, and I get A+ with 0ms on bufferbloat. Of course, this is an extreme case, But, I state this to say that everyone connection will not be the same.
One thing is for certain; once you get your connection to A+ with 0ms bufferbloat. You do have a more enjoyable experience in gaming. I say anything below +5ms is fairly good. But, 0ms is best.
Just take a little time and get your congestion control right for your bufferbloat. You'll get it. R3 is 100% capable of getting you 0ms.

Guys, if you have full gigabit speeds, try Advanced Speeds set to 1000 for both up and down.
Then on Congestion Control Mode, set it to Auto. It will lower your speeds slightly, but the trade off is much more stable ping. Allowing me to achieve A+ from A when it was set to Low Latency Only.
Depending on what you get with Low Latency Only, you might see an improvement to the ping values especially when you set it to Auto.

Even though there's not much reason to having low latency when you're not gaming, it might be great for Home Automation devices to respond to your actions more promptly thanks to having lower ping.



On a side note, 0ms ping for both up and down is now easily achievable at higher speeds than last time where I need to set it a lot lower in CC.

Guys, if you have full gigabit speeds, try Advanced Speeds set to 1000 for both up and down.
Then on Congestion Control Mode, set it to Auto. It will lower your speeds slightly, but the trade off is much more stable ping. Allowing me to achieve A+ from A when it was set to Low Latency Only.
Depending on what you get with Low Latency Only, you might see an improvement to the ping values especially when you set it to Auto.

Even though there's not much reason to having low latency when you're not gaming, it might be great for Home Automation devices to respond to your actions more promptly thanks to having lower ping.



On a side note, 0ms ping for both up and down is now easily achievable at higher speeds than last time where I need to set it a lot lower in CC.

Yeah there is good evidence that they muck around with your aim, where players spawn etc to 'even' the playing field. 

Brilliant from the guys at Netduma, showing full speeds and very little adjustment to get my A+ on waveform, gaming now seems more crisper with hit detection on both PC and PS5, pass the thanks to the team @Netduma Fraser

Hello everyone, I will make a new topic with the firmware when ready so you can download it and try, I won't be sending it to people individually so no need to ask

We haven't pushed the firmware and we won't at the moment, it's being tested, once I'm happy with it I'll let people try it tomorrow.

In fact yes, Sunday is historically the first day of the week! 😀

I believe it is the CPU issue you're experiencing, the firmware is due this week and not only will the CPU usage be drastically reduced, the higher ping/jitter caused by it should be resolved as well. As lot of fixes/improvements in this one I believe.

Hi guys,
Ive been keeping an eye out for the new firmware to address the issue highlighted with high CPU usage. Just wondering if there's a hotfix coming soon?
It seems the high CPU usage is causing quite a lot of instability with my ping, so I'm currently reverting to use ISP modem while awaiting the new firmware..
Here's a few screens of my ping stability with the R3 vs my ISP Modem (Vodafone UK).
R3 Ping (firmware 4.0.23) - connected via Ethernet:

ISP Ping - connected via Ethernet:

In both instances, nothing else was running on my internet, both are taken from my PC at different times - connected via ethernet cable.
Background info on my setup:
I'm on firmware 4.0.23 - I've been testing this out for the last few weeks. My connection type is DHCP. I have Steady Ping is disabled / Congestion Control at about 87% on dl / Ad Blocker is disabled. I have UPNP enabled in both ISP modem and on the R3. ISP modem I've set up the R3 within DMZ and with a static IP Here's a snapshot of my current CPU usage:

Just to rule it out - the router is on a flat surface and well ventilated - so I don't think it's a cooling issue.
Just while I'm posting, I have a few other minor bugs I thought I'd mention:
IPv6 doesn't seem to be working (as you'll see in the ping graphs above R3 version has a IPv4 address for Google test), I have IPv6 enabled in both WAN/LAN settings. Ethernet internet takes an abnormally long time to connect - about 30-40 secs or so, vs 5-10 secs with ISP Modem. I've included attached a log in case it helps at all. It would be good to get an ETA on the new firmware please - hoping there'll be a hotfix soon!
Thanks!
R3_2024-01-23T16_02_55.912Z_logs.txt

Looks like you have Geo-Latency enabled there which is probably why. What web browser are you using to try to change ping assist? Are you connecting to the interface using HTTP or HTTPS?

I'm not entirely sure at all how this is remotely possible... but two things to point out.
1) -- I connected to a server so far outside my Geo Filter, I can't quite wrap my head around it... and
2) It claims my ping is 30ms from router... but my in-game shows quite a different story (125ms, as it should be).
So, why am I connecting that far outside (at all) my geo-filter, and why is it so horribly reporting the wrong ping from the router?

For those with the seemingly higher pings when using the R3 please do the following, ideally testing with PingPlotter and offering a plot from your ISP modem as a comparison:
Ensure the upstream/ISP modem/router the R3 is connected to is setup with the R3 in its DMZ or in modem/bridge mode. 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 If you have multiple ethernet cables test using different cables connecting the R3 to the modem/the R3 to your device Disable IPv6 in LAN/WAN Please state if you are using PPPoE, VLAN or DHCP identifiers Use a different DNS such as 1.1.1.1 / 1.0.0.1 As a test make an Internet rule to the device and allow ALL traffic then test, is there a difference? (Settings > Internet Rules) As a test put the PC in the DMZ (briefly for the test then remove), then do a test, is there a difference? Remove all prioritizations from SmartBOOST including activities/devices If the above doesn't help disable SmartBOOST entirely from the 3 dots menu top right of the page  > Settings then test 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 Disable Adblocker Ensure you have your correct speeds entered in Speed Test > Advanced With SmartBOOST enabled, adjust Congestion Control in Ping Optimizer > Advanced and have it set to Always On and ensure speed test bypass is disabled Ensure you're doing this test over a wired connection - NOT WiFi Ensure in WAN/LAN Settings that the speeds of the ports are at 1Gbps Remove any port forwarding/DMZ/static routes you may have set 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. 

This is in line with what I experienced using the simple Bufferbloat tests. Higher jitter and higher lag spikes when connection was on idle.

So here's an example. CC Enabled (Speedtest Bypass Off) with 100/100 for both the R2 and R3 + R3 w Steady Ping

R2
25th %ile: 3.2 ms
75th %ile: 3.9 ms
95th %ile: 4.3 ms
Jitter: 0.5 ms

R3
25th %ile: 7.3 ms
75th %ile: 9.5 ms
95th %ile: 12.6 ms
Jitter: 1.6 ms

R3 with Steady Ping
25th %ile: 3.5 ms
75th %ile: 4.5 ms
95th %ile: 7.2 ms
Jitter: 0.8 ms

@Netduma Fraser
I did two tests. configured the provider's router in bridge mode. I configured PPPoE on NetdumaR3 and on an older Tp-link.
1) Provider router(bridge) -> Netduma-R3 = 42ms in EAFC24, 21ms to 8.8.8.8
2) Provider router(bridge) -> Tp-link = 31ms in EAFC24. 16ms to 8.8.8.8
The bad part is that with R3 the ping fluctuates from 35 to 42. With tp link it stays constant at 31.
Played with the same frend in the same server to be sure of results.
It's clear something bad happen with the R3 router in this moment.

Sorry for the late reply, as you and others have mentioned there seems to be a higher/more unstable base ping when using the R3 that some people are experiencing. I've passed all my findings over to the team so they'll look into it as soon as they're back 

@Netduma Fraser / @Netduma Admin
After testing, I've found IPv6 must be disabled in advanced LAN AND WAN settings in order to de-activate Steady Ping
*Note for anyone that does this, you'll need to reboot the router afterwards so the router can re-configure DHCP*
I've also seen on another thread congestion control/QoS doesn't work unless IPv6 is fully disabled in both WAN/LAN settings too.
I'm using the beta firmware 4.0.23.
I have split up 2.4/5GHz bands and I'm using 5GHZ only for wireless devices.