DARKNESS

Okay, so for you, "problem" rhymes with "breakdowns" in the IT world, which you clearly don't know much about, especially here, since it's supposed to be a gaming router, so latency and other factors should be optimized as much as possible. Well, in these logs, that's not the case. The router, especially the processor, is working unnecessarily and haphazardly, which affects the stability of the system and therefore the router... Basically, just because your car starts and runs doesn't mean it doesn't have a problem... But since it's you, I can understand.

@18RayFYour case is uncommon but not unheard of. What stands out is that you're using DHCP, which typically operates with an MTU of 1500. However, your ISP is clearly providing an MTU of 1492, commonly seen with PPPoE, and when the MTU exceeds the limit set by the router, fragmentation occurs, which can lead to issues like the one you experienced. In other cases, this might manifest more noticeably, such as through packet loss. It is not an issue on the router side as the router uses the most common configuration. 
@KinGzzyMost of what you said isn’t even an issue; the time going backwards is literally just the DPI reading the packets, and as you are using the AI, which you are, it doesn’t tell you the most obvious thing, which is that IPv6 is disabled.

Hi
According to the logs, your router is suffering from major software instability.
1. IPv6 configuration problem (odhcp6c)
2. Script and TLS errors (cli.lua)
3. Time instability (Time went backwards)
4. Very frequent DHCP renewal (udhcpc: lease obtained, lease time 600)
5. Memory cleanup (drop_caches) USER root cmd echo 3 > /proc/sys/vm/drop_caches
6. Processor instability (Time went backwards)
7. The conflict with "DPI" (Deep Packet Inspection)
In your logs, I also see: user.info dpiclass-daemon: Daemon shutdown user.warn overwatch: Changing category of appid=161... to VPN
Your router is suffering from major software instability. This isn't just a minor connection error; it's the DumaOS system crashing because it's trying to handle too many things at once.

@purpleandgold33You shouldn't rely on it since it's inaccurate and requires an update. I believe they are working on a fix to improve its accuracy. In the meantime, adjust your sqm manually.

You just admitted it lag spikes when using it though??

@Mach3rYou won’t get accurate results if the speed test bypass is enabled. You need to disable it. Also, set the congestion control mode to "Always On."

@BigPapytoIt’s likely an issue with your Ethernet cable. Try replacing it with a new one or using a different cable to check if the problem persists. Don’t use the same cable. I would guess you’re using the one that came in the package, which some came faulty. Just something to point out....they may work as intended but randomly do drop to 100Mbps instead of using full throughput due to bad coiling, etc.

You made one topic which I replied to within a few hours and then you never replied again so we can't know you're still experiencing an issue if you don't tell us. It sounds like you've tried to get support from NTGR this whole time and not had any success but then have ranted here instead which would have been the better place to get support considering we made DumaOS and NTGR didn't. Either way, glad you've got some relief now, we're still happy to help if you want it.

This is your topic now I just meant in general and going forward. 
In your topic about the issue you just referred to, we offered, even though you were outside the warranty to provide a replacement for you, you just needed to email us. That was 2 years ago. Checking emails you emailed us last month about this and at the time I replied saying "You weren't left without a resolution, it does say there that we would arrange a replacement for you. However, as you've waited 2 years to contact us a replacement is now no longer possible, we don't sell the R2 anymore and don't have any spare. We also don't provide a repair service. I can offer you 30% off an R3 if you're interested but that's the best I can do now. You could sell the router as spares/repairs on eBay." A month on that hasn't changed.
We do care about customers being happy, that's why we originally offered to replace it outside of warranty. 
 

@fletcherjames1It could be the fact that there a conflict with the IP with the modem so in this case you'll need to change the IP of the router rather than it having 192.168.1.1 change it to 1.1.1.1 or something preferable...

@fletcherjames1Go to Settings>LAN Setup>IP Address>Apply

Well I can see your problem! Your monitor is upside down so the internet is falling out of the monitor. Turn it around the correct way and you wont have any internet leakage. 

You're posting here asking for help and yet you will not take the advice of someone who has been providing support since the company launched 11 years ago. I don't quite know how you think that you know more about the problem you're having than I do but I'm sorry to say that what I have said is correct. If I wasn't correct then everyone would have the exact same issue and they don't. Regardless, if there was an actual issue that needed a firmware update, saying fix the issue is extremely unhelpful, it provides no information about the scenario in which your issue occurred, your full settings, setup etc. If you're not going to engage with the support that you have requested I don't know how else I can help you.
In order to really fine tune your Congestion Control percentages you should follow these instructions:
Follow this guide https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ while downloading & start with 95% for Congestion Control (set to Always), check results, decrease by 10%, check, decrease by 10% etc, until you get to a value that is pretty good & then try 5% either side of that value to see if it can be improved. Download & Upload on Congestion Control don't have to be the same value & you may have a better experience with differing values.

Yes playing on a further away server is likely to worsen your jitter.
No, the Geo-Filter and your bufferbloat test are not connected. 
The Geo-Filter shows game servers you connect to, it is highly unlikely to show the bufferbloat server you're using. The bufferbloat server could be anywhere, that's the point, doing the test at different times of the day could have you connecting to different servers and therefore getting different results. This is why I as well as Darkness said not to put too much emphasis on its results. Yes it is testing your network utilizing a server for the test. Here is an analogy for you.
Your ping without bufferbloat is like driving your car on an empty road, you're going to a location and you know how long it will take you to get there, for example 20 minutes. This could be your baseline ping for example 20ms. 
Your ping with bufferbloat is like driving your car on a road with traffic, you're going to the same location and you know how long it should take you to get there (e.g. the 20 minutes), however due to the bad traffic it actually takes you 40 minutes to get to the same destination. Your ping here could be 40ms for example.
In regards to the server the bufferbloat test is using, without a destination to test it against you can't get a ping value or a destination to drive to. Now imagine your place of work changed depending on the time of day and the time you start work changes as well therefore it could take you anywhere from 10 minutes to 1hr to get there. Would you be so confident to say that it takes you 10 minutes to commute to work everyday? Without knowing the server the bufferbloat test is using your results cannot be 100% trusted. That's why the pingplotter suggestion is better, you know the exact server you're using, you do a test to establish your baseline ping (ping without bufferbloat) and then apply traffic and your ping raises, just like road traffic extends your journey time and then you apply Congestion Control to limit the effect that traffic has on your ping. 
There really isn't anything else we can advise honestly:
You've established it's an issue without the R3 - that automatically eliminates us personally from needing to troubleshoot with you We've advised you select the closest possible servers, this will help lower the ping and improve stability (jitter) We've advised you on how to effectively test and set your Congestion Control percentages to lower your ping and improve stability when bufferbloat would ordinarily apply

@fdsYes, that's normal; that's what QoS does. It manages your packets to prevent any queue buildup. What do you mean by "slayers"? You don't need more than 5 Mbps to play a game.

@fds
By monitoring the game during the bufferbloat test, you can detect abnormal spikes or packet loss. If such issues occur, continue fine-tuning the settings. The goal of SQM (Smart Queue Management) is to optimize the network, prevent overloading, and maintain consistent latency. Every connection is unique; for instance, my connection has 2G download and 400 Mbps upload speeds. To ensure stability without packet loss, I adjust it to 180 Mbps download and 60-80 Mbps upload. This setup consistently earns me an A+ rating, even during ISP congestion. Throughput is less critical for gaming; latency and stability are the key factors. While other elements may influence performance, the most important ones are within your network, which you can control.
It seems that you want full throughput when you're not gaming, which is achievable through the router settings. Simply select the low latency option, and it should only be activated while gaming, if I recall correctly.

If anyone is struggling connecting with skybroadband using a third party modem like an vigor 130 just follow the steps in the picture below.
 
Sky uses an identifier so we need to enter that into the R3 as below 👇 
 
WAN settings then PPPoE then type whats in the picture below exactly and apply and its good to go ! 
 
remember to download the latest firmware too 

@Wr3ck3rIt's a known issue currently being addressed. It doesn't impact the router, and you can use speedtest.net as an alternative.

It's right there bro. Right before your eyes.  "Slightly above average". Read it.

@Kahari
Yes, I recommend performing a factory reset on the modem to ensure optimal performance and stability, especially since it was previously reprovisioned from the problematic version V6.01.03. This version caused significant issues, prompting ISPs to roll back the update due to widespread complaints about its faulty patch. Additionally, confirm that your WAN and public IP addresses are correctly configured in the R3 interface. Before proceeding, review the modem logs—if you notice a high number of uncorrectable errors, the issue is most likely with the ISP rather than the router or other equipment.