Iced Soul

Fala, meu querido!

Muito obrigado pela disposição em me ajudar com tantas dicas, muitas inéditas pra mim. Vou te dar um toque por mp, ok?

DMZ + PC =  WARNING !
Ne jamais/jamais.... faire ça !

We'll fix the PPPoE issue, thanks for letting us know.
Disable Geo-Latency and Ping Assist, make sure you're enabling the Geo-Filter before you launch the game/client and if you change Geo-Filter settings while on the game then reboot the game and it should all stay within your radius.
We're aware Ping Optimizer isn't 100% reliable currently but the ping at the start is your base ping - the ping you have before you do anything on the internet so it's established what that is to the server it is using (the ping won't be the same as wherever you may see your ping). It then simulates a heavily used network and re-tests the ping, this is where you'll see an increase in the ping. It then repeats the tests but adjusts the Congestion Control percentages to find the percentages that allow you to have a heavily used network with minimal difference in your ping. So what you described is the optimal outcome and exactly what you want it to be doing. 

On Windows, there isn't much you can do about the network.
You can tag your applications with DSCP tags if your router supports packet prioritization using DSCP.
Some people optimize their Windows using the registry.
Google is your friend, but if you want, you can test software.
Windows:
Resource Monitor (resmon.exe) allows you to see which processes are consuming bandwidth.
Third-party tools like NetLimiter or cFosSpeed allow you to limit or prioritize certain applications.
Router:
All routers these days, or 99% of them, have QOS.
QoS → its main role is packet classification and prioritization (e.g., gaming > voice > download).
Bandwidth control → is achieved through mechanisms such as HTB (Hierarchical Token Bucket), HFSC, or FQ_Codel/SQM, which manage efficient throughput distribution.
To be more technically precise:
QoS ≠ direct throughput management → it's a "who comes before whom" logic in the queue.
HTB or equivalents → allow hierarchical classes to be defined with minimum and maximum bandwidth allocations (per user, per IP, per protocol).
In modern routers (e.g., OpenWrt), the two are often combined:
Classification (QoS) → to identify sensitive flows. Scheduling/Shaping (HTB, FQ_Codel, CAKE) → to efficiently allocate and limit bandwidth.
So, to put it simply:
QoS = packet priority.
HTB/HFSC = bandwidth control = actual bandwidth allocation.
For gaming, both are very important, especially if you're playing on a PC. Having a 240 Hz monitor isn't enough.
Optimizing Windows is important to avoid input lag in games.
And when it comes to networking, there's no magic formula: a very good ISP connection and a good router to prioritize game packets and other...
In your case, that's gaming, especially Call of Duty.
This means you need to make sure your game takes priority over other tasks.
No packet loss, no buffering, and no excessive ping; your game remains the top priority, even when downloads are overloading your bandwidth.

Most of the issues with PPPoE that we've had in the past have usually been with QoS on the upload side not working with it which has been resolved. The issue currently is that a small percentage of PPPoE users are experiencing disconnects, this is most likely due to the nature of the connection method (i.e. that it 'logs' in to the internet service and can have a timeout on it) but we will fix that.

Fique a vontade 

Fala, meu querido!

Muito obrigado pela disposição em me ajudar com tantas dicas, muitas inéditas pra mim. Vou te dar um toque por mp, ok?

ACC is mentioned in that link I provided but we haven't provided any more information about it just yet. You can enter the poll here to be in with a chance to test it early on if you fulfil the requirements for this early test: https://forum.netduma.com/topic/60353-answer-this-topic-to-be-in-with-the-chance-to-beta-test-a-firmware-with-new-features/
 

E ai cara, vou mandar a msg inglês. Tmj 
Hey man! I read your posts and I’ll try to help. I also play COD (Warzone) and had a lot of issues with my internet, but I managed to improve it a lot. Went from a 1.3 K/D to 3 in WZ. Hopefully this helps you decide which setup to go for.
 
The Netduma R3 is really good at what it’s made for. The QoS works well and the geofilter is by far the best feature for COD/WZ. But it does have some issues, especially with PPPoE. If your ISP uses PPPoE, keep in mind that the R3 doesn’t handle it well. Here’s what I did to fix my connection:
 
Step 1: Call your ISP and ask for a static or public IP. This takes you out of CGNAT, which usually gets overloaded during peak hours. Just this change alone gave me about 50% improvement.
 
Step 2: Put your ISP’s ONU in bridge mode and let the Netduma handle the whole network (QoS, packets, IPs). This gave me another 20% improvement.
 
Step 3: Swap your onboard NIC for a PCIe card with the Intel i226-V chip. Highly recommend it! Even footstep audio got cleaner. This chip avoids micro-delays and improves reg hit. I’d say around 15% improvement here.
 
Step 4: Replace the ISP’s ONU with a switch that has an SFP port. This improves the network infrastructure and also solves the PPPoE problem with the Netduma, since the PPPoE dial-up is handled by the switch, leaving the R3 only with QoS and traffic management.
👉 But keep in mind: depending on your ISP, this swap is pretty technical, so I only recommend it if you already have some networking knowledge. For me, it added another 10% improvement.
The rest is just using quality cables and optimizing your PC.
 
Overall, I do recommend the Netduma R3. It still has things to improve, but it offers some great features.

As I mentioned before that is peak time congestion from your ISP, nothing has changed on your side when that happens so there is nothing you can do on your side at that time. When ACC is available for the R3 it may help with that but I can't guarantee it. 

Si ton FAI a de la congestion aux heures de pointes... Tu ne peux pas faire grand chose, le QoS est géré en Local pas en Amont de ton FAI !
Si tu as plusieurs lignes à disposition.. le mieux est d'utiliser celle qui n'a pas de congestion aux heures de pointes pour le jeux !!!!
 

Okay that would explain that ping then, I still don't believe you need it for SQM but yes it does have the same implementation as the R3 currently although in Early Access though you can try pre DumaOS 4 but you won't get many more updates for that router.

You're using it with 1 device only? Exitlag may improve the routing to the game servers if your routing is less than optimal. That's a fairly high ping, where abouts are you located?

SQM isn't really new per se and is already what we offer with our QoS solution which will only get better with the next update we're working on. 
It really depends on how you're going to integrate your gaming router into your setup. If for example your setup will be:
Main Router (All Devices Connected) > Gaming Router (Just Gaming Device Connected)
then QoS/SQM is irrelevant because the router won't be able to control the entire network. It would only be able to control the gaming device which from the gaming router perspective isn't competiting with any other device. However, it's actually competing with every other device connected upstream to the main router. If you really wanted to do it this way then the main benefit you would get would be from using the Geo-Filter on the R3, something no other gaming router has.
If for example your setup will be:
Main Router > Gaming Router (All Devices Connected Including Gaming Device)
or some variant of that then QoS/SQM is a lot more relevant as it can control most if not all (it really should control everything for max effect) of the devices on the network. In which case I'd still suggest the R3 for our current QoS implementation but then even more so for the next iteration of QoS that we have planned.

This blog may help: https://netduma.com/blog/how-to-fix-bufferbloat so our current implementation, Congestion Control & SmartBOOST is literally a form of SQM. The ACC referenced there is what I mentioned we're also working on that goes beyond this. 
As before, the fact you have a whole connection I assume purely dedicated to gaming even further reduces your need for QoS/SQM as that's only working on your side of the router to reduce bufferbloat/lag etc but with literally an entire connection just for gaming it really isn't needed. So if that is correct then the R3 would be the one to get with the idea that ACC will be more useful for you in the future.