Moofda

Can't believe it's been 11 years since I joined the forum ,  during that time I have had the R1 / R2  XR500 with R2 OS and now the R3.   Today my R3 is plugged into my Asus RT-AX88U Pro ,   Just a little bit on the Asus :  Rock solid piece of kit with great WIFI coverage and a good amount of gaming tweaks within the  OS  including various different types of QOS , on average we have around 22 wired and wireless devices connected to the Asus no issues ever .  Only the Xbox is a  wired connection  to the R3 ,    I have flip flopped from both routers over the last few months and always go back to the R3 from a connection perspective it just feels much better , for me it is best in class it does what it is supposed to do from a gaming / connection perspective .
HOWEVER -  I had some time over the Xmas break off work and decided to plug the R3 directly into my ONT ,    so all devices connected to the R3 as it is designed to do ,  BTW just to say I think the OS  on the R3 is excellent from a visual perspective and provides so much information and options to fine tune , much better than the Asus in my opinion , the following is what I experienced over a full week  :
Daily drops in WIFI or internet connection  longest period of connection 1.5 days before I re boot  WIFI would not reach as far as my Asus , ring door bell and Hive would not function correctly  Family complaints  Gaming was even better   Where I am going with this ?   Is  this a hardware or software problem ? , I have tried to live solely  on the Netduma router previously but it never delivers on a stable connection as my default network router when everything is connected to it .  If it is  hardware issue hen I for one would be willing to pay more to have an Asus type performance with the Netduma OS .   I know we have had the Netgear experiment but not sure that is still an option mine died a long time ago . 
In closing I love the Netduma OS , it is back now plugged into my Asus and in my opinion gives me the best gaming connection on the market without doubt . It is just not capable of being a default network router managing all devices .  You could I suppose without being dis respectful call it a one trick pony ..... but hey it's one hell of a trick  
 
 
 
.   
.      

I’m going to push back on this a bit, because the conclusion being drawn here doesn’t line up with how online games or networks actually work.
I’m an Enterprise Lead Network Engineer with over a decade of experience designing and operating large-scale, latency-sensitive networks (factories, global WANs, DCs, SDN, etc.). I am also a professional competitive CS2 and FortNite player. From a technical standpoint, a consumer router cannot “manipulate lag compensation or hit detection” in the way you’re describing.
How hit registration actually works:
In modern multiplayer shooters (including CoD), hit detection is authoritative on the game server, not the client and certainly not your router.
The general flow looks like this:
Your client sends input events (movement, aim, fire timestamp)
The server rewinds game state using lag compensation
The server determines whether a hit occurred
The result is sent back to all clients
Your router never sees:
Player hitboxes
Server reconciliation logic
Lag compensation algorithms
Damage calculation
It only sees encrypted UDP packets with timestamps. (along with a few checksums that are used on the backend to determine whether there has been any manipulation to the data stream, but that is entirely dependent upon game and AC used).
What lag compensation really is
Lag compensation exists to normalize different client latencies, not to “reward” or “punish” certain players. If two players fire at nearly the same time, the server rewinds state to each client’s perceived moment and resolves the outcome.
This can feel unfair at times, but that’s a function of:
Tick rate
Interpolation / extrapolation
Server load
Packet arrival variance
Player movement prediction
Not the brand of router.
What routers can affect (and what they can’t)
At Layers 1–5, almost every modern router you listed (OpenWRT, MikroTik, pfSense, Ubiquiti, Asus, NetDuma) is doing the same fundamental job:
NAT
Stateful firewall
Packet forwarding
Optional QoS / shaping
This is the ONLY thing that you might be able to argue NetDuma does 'better' than others. However, that is merely if they do it 'out of the box' vs. others that may not considering it's all adherent to RFCs and standardizations, dscp values, etc. 
If bufferbloat is already controlled (which you explicitly said it was), then:
Latency is stable
Jitter is minimized
Packet loss is negligible
At that point, there is no mechanism for a router to selectively improve hit registration. It cannot reorder server logic, alter rewind windows, or bias combat resolution.
If it could, competitive esports would ban consumer routers overnight.
Why it feels different
Perceived improvements usually come from:
Different matchmaking servers or routes
Temporary changes in server load
Variance in opponents’ latency
Session-to-session network conditions
Confirmation bias (especially after hardware changes)
Humans are very good at pattern-matching and very bad at controlled experiments, especially when adrenaline and competition are involved.
The key point
If a router could truly “manipulate lag comp”:
It would be detectable by the game developer
It would be considered cheating
It would be patched or blocked immediately
No consumer router has access to the data or control plane required to do that.
Final thought
If you’re enjoying the R3, that’s totally fine. Stable latency and good QoS do matter. But attributing gunfight outcomes to router-level manipulation of hit detection isn’t technically accurate.
The network delivers packets.
The server decides who lives and who dies.
Everything else is perception.

A simple router/AP created to piggy back off another Primary router with its main, or maybe sole function, being a geo filter primarily. 
I think the overwhelming majority of Netduma users over the years use the router primarily for the geo filter specifically. 
 
If you look at most of the complaints or problems over the last three generations of routers, the majority of the problems stem from basic expectations of routers in general: Disconnection issues, bunk wifi/ether speeds, qos failures, ipv6 failures, etc, (there are many).
 
However, not as many complaints about the Geo-filtering, except using your PC as a PC in device manager while geo filtering, which doesn't work correctly. (Most recommendations say to make your PC a console or PS4 for best results). 
 
Enter the the Geo box.
 
No Wi-Fi, only wired. (Your users are already wired for the most part for intended geo filtered devices) Primitive in function, without any extra fluff or desire to be an actual router. Just a device to accommodate an existing router with geo filtering and additional attributes that may help gaming on said wired device. 
 
You could even go wild and offer an app for windows/PC that solely focuses on geo filtering. 
Just an idea. 

It does work as a PC but the thing is the game changes so often that the service becomes out of date and so its a bit of a chase to keep it updated that's why I usually suggest the console method as that always works

It won't work in duma without being able to have a username/pass. Nolag VPN is meant to interact with open vpn connect. Even if you make your own COD VPN, by using your own vpn provider and routing the match making server, as well as all the game servers you listed here, it does not work with hybrid VPN in netduma correctly. You can connect to it successfully, but it routes your entire device to the VPN server, not just call of duty.  I've tried all sorts of options, like "only vpn these services" with call of duty selected, but it does not work. When you select only vpn call of duty, it shows up as your default network config in game. I've tried the port options as well but haven't had any luck. 
I just use the wireguard client and or open vpn connect on PC and use what you have above with my existing vpn provider. I'll say it doesn't really make a difference at all, where as the geo filter appears to have way more of an impact for having more random lobbies. Although at the expense of longer lobby que wait times.  Just my 2 cents. 
 
 

Please fix the issue, I still rock R1.

Hopefully as soon as possible, because playing Coda is impossible, not to mention the main function of the router: GeoFilter.

Thank you, I'll pass those on!

That is a cool idea, the problem with that is they can have A LOT of servers clustered in one location so the list of potential servers could be huge

Honestly the geo-filtering is your best tool for potentially getting better games. It naturally adds an extra layer against a bigger pool of sbmm. You can see the difference on where the matchmaking takes you vs it on and off. The steady ping feature at least in my findings, works great for hit detection, especially in servers you have the least amount of ping to.

Honestly the geo-filtering is your best tool for potentially getting better games. It naturally adds an extra layer against a bigger pool of sbmm. You can see the difference on where the matchmaking takes you vs it on and off. The steady ping feature at least in my findings, works great for hit detection, especially in servers you have the least amount of ping to.

Is the R1 supposed to have all the same cloud updates as the newer routers? Our Ping Heatmap matches the one above posted by alecjb12. Router OS version is 3.0.207.

Tried resetting router settings to factory. Every time I "Resync Cloud", the logs say "Ping Heatmap has finished merging data from the cloud!"

We don't give out any ETAs but we're looking into it currently

The open vpn configuration worked fine through the hybrid vpn section of duma os, just not the wireguard. I was doing it simply to test the function, it worked fine on my r1 for both configs. I have a proton vpn client for windows though, so when I want to use wireguard profiles that works just fine, so no worries meow. 
I was testing a wireguard vpn server through dumaos in the same state as me and nearly the same city, but yes you are right, they are trying to mitigate people using vpns to enter very distant servers (ping wise).

My ping varies between 70 ms and 200 ms, and I cannot connect to the CA server only.

Yeah that is a conundrum as well tbh, something I will need to discuss with the team when they're back

The white circle will be because you allowed it and then the triangle will be because Ping Assist blocked it. The most likely cause is there are a lot of servers in that location that are mislocated which it's trying to connect you first, with the IDs we can check and move if needed

Could be a few things, the speedtest.net server being used is similar to the above, however you can change this so check it's one of the closest to you. The other thing could be that the cable connecting the R3 to the modem is limited, in which case try swapping out the cable, even if it is the one we provided and check again. Test over ethernet if you can ideally.
Otherwise for WiFi try this:
Split the WiFi bands, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

Having it as a PC requires you to select the specific game and this service/game selection uses information to determine that it is that game you're playing, games are quite fluid and what we use to determine it is that game changes so it can become out of date. By switching you force it to use the Games Console service which makes it rely on ports instead which don't change and also is more broad so you can filter without changing game each time.

Ahh yep, that makes sense with approving stuff outside the radius, I had forgotten about that. And yeah I totally understand on the support aspect of buying it used. I'll have to take a look and figure something out. Thanks again for all your help. 

It is a big deal in the sense that you absolutely need to have a connection to it to play but definitely nothing you need to worry about seeing at all.
Good to hear! So essentially the radius acts as a temporary allow/deny in a way, allowing anything within and blocking anything outside, allow/deny does this but permanently and will apply regardless of your radius. I.e. if you've allowed a server but it's outside your radius the next time you play you could still connect to it and vice versa, a denied server inside your radius will still be denied. It is good in the sense you could build up a list of servers that play really well for you and deny the servers that don't and over time you should then have more good games vs bad. 
There are extra features on the Geo-Filter with DumaOS 4 such as Geo-Latency and Steady Ping and I'm not not sure if it's in that version or not but country specific filtering so it depends what you're after really. Just a warning though, getting an R2 second hand, if anything goes wrong with it we couldn't replace it - we'll obviously still give you support but anything major we can't replace it. We have a Black Friday discount on the R3 right now, maybe check that out and see if it's worth it for you.

Oh right I gotcha, it should still get the latest cloud information but IPs are never 100% accurate so it's like pushing a rock uphill! They don't currently but it may be implemented in future. You can just report them in any topic like this one really, if you have some let us know and I'll pass them on to be corrected. 
That one sounds like the authentication server in Ireland so that'll be fine.