I’m looking for any ways to make hit reg the best in bo7. I have the xr1000 on 1000d/50u fibre plan and play on pc ethernet + static ip. 

I’ve seen bufferbloat the most, but also nat type, adapter properties via windows etc get thrown around a lot. I play on very low ping so just trying to get the most out of it. 

I tend to feel inconsistencies here and there in terms of hit registration in bo7 at the moment. Sure, some could be skill issue + frame drops perhaps… However i’ve troubleshooted so much that the rest just seem to be wacky hit registration.

I tend to notice it the most when shooting players about to run behind cover. Aswell as a fair handful of gunfights id otherwise never lose up close, i.e me: full health no shots missed, shooting them first to half health before they even start to shoot back and the likes.

I’ve got a solid understanding thus far of most internet stuff so if any guidance or optimisations can be given to nailing this down, it’d be much appreciated! 

For almost a year I've been using GF and GF only .  No Smart Boost , Hybrid VPN , Ping Optimizer, Device prioritization, port forwarding etc. This feature alone makes R3 a great buy.  

And don't get me wrong. I took my time (a year or so) to post this .......  Let me explain.

I consider myself a decent player. Slightly above average. Targeting nearby servers will probably give you a nightmare. Sweaty lobbies full of "orange" ranked players sliding corners, jump shooting and breaking cameras.  So I decided to turn cross play off and move out of this "nearby-low ping hell hole servers" to a slightly distant one with approximate 100 ms ping, and magic happened. Easier lobbies 90% of the time but a long waiting time to join  games.  Whatever. I'll take it. Ever since, I can't wait to play COD again. From now on all my household Internet needs are covered by my IP's router while my console is hooked to my R3. 

Anyways , thank you NETDUMA for this amazing feature. 

I know the quality is ass.  im testing things with my obs settings.  but this is the best raw footage I could pull  since theater mode would have a slight delay.

combined the geofilter ability with exitlags routing features and got some of the best hit detection ive seen in the 4 years ive had this router.  thie duo isnt perfect. but when it works, it is absolutely wild. 120-30 this game. ( most my deaths were stupid challs or me being a moron)

one wildcard im willing to throw out there is that im also using the most busted weapon in the game.  but yea

I mainly play Warzone, living in Germany, geo-filtering to the US.

My problem:
I´ve done all tweaks, went through several posts/topics here and also allowed all specific ports for the PS5 in the "Port Forwarding". 
I set my GEO filter to East-America (I live in Germany) with radius of 2000km, so several servers in this circle. Everything works fine, also the authentication to the Dublin server when launching CoD.
Even when I search for a game it directly searches for a match <100ms ping, which shows the filter is working.
BUT: It will never find a match. No matter which game mode I play. I already did that whole thing (delete device, resync cloud etc..) thousand of times, rebooted, etc. 

I have nothing changed on the Netduma OS, only IPV6 disabled, which gives me insane bufferbloat results. (A+) Thanks for that, Netduma! 🙂
Strict Mode on, Filtering enabled, Ping Assist off, Geo Latency off. 

I always search with console only crossplay so basically crossplay off.

Only thing I find strange is that I am in STRICT NAT Type in CoD , could that prevent me from getting into games? 

I really would appreciate an answer from someone who is playing on PS5 and is using the GEO-filter in a similar scenario successfully. DM or Discord Chat also appreciated. 

Thanky you in advance for your support!

write it down 

also in QOS port prioritization  DO U USW IT GUYS  And Work for you For BO7? Share urs guys will try it 

try it out.   I kept mine on  default value

NetDuma R3

DumaOS Version 4.0.540

App Version  v4.0.192

• Setup: I have a PS5 with BO7. I use a Netduma R1 router that is older. I live in southern Argentina, very close to Chile.

Netduma R1 NOT involve

• NAT Type 2.

• Direct to modem: I can search for parties and matches quickly.

• Typical servers found: I usually get Rio de Janeiro and São Paulo. 

• But I know from Netduma, that there is a Chile server now.

• Open Matchmaking playlist.

• Usual ping: about 40 to 50 ms. I feel at a disadvantage vs players near Brazil servers.

What changed briefly (FREE WEEKEND)

• During one day on the free weekend, likely Saturday, my minimum matchmaking ping showed 29 ms.

• Those matches felt local and smooth. I hit killstreaks and the gameplay felt fair.

• My conclusion from that day: I likely connected to a Chile server, probably Santiago, which fits my location.

• After that day, my minimum search ping went back to about 47 ms.

• I no longer get those low ping Chile matches, even though I am close to Chile.

Netduma R1 Involve

• The heatmap does not show Black Ops 7 reliably for me.

• On the Geo Filter map, I sometimes see a Chile server, but when I restrict the area to only that server, I still do not find matches.

• If I expand the allowed area to include São Paulo, I still often fail to match. (Fail to connect to host)

• To match quickly, I have to unplug the R1 and connect my PS5 directly to the modem.

Networking steps I tried

• I set up port forwarding for PlayStation. 

• I put the PS5 in the DMZ.

• I toggled the Geo Filter on and off.

• Even with those steps, the R1 still blocks or slows my matchmaking compared to the modem.

• (For reference) Battlefield 6 found matches using R1

How it feels in game and my questions

• On Brazil servers, time to die feels instant. I shoot first but die first.

• On the brief Chile matches, gameplay is smooth, responsive, and fair. The difference is big.

1. Why does my Netduma R1 prevent or delay matches when the modem works fine

2. If there is a Chile server near me, why do I almost never connect to it now?

If needed, I can send a screenshot of my Geo Filter and current R1 settings.

We do frequent updates to the Geo-Filter cloud which contain the latest information about server locations, but sometimes a few servers might be missed.

If you find a server which seems suspiciously out of place, you can submit the information into the form below. We'll figure out where the server is supposed to be, and we'll move it in the next update!

Thanks so much for helping to make the Geo-Filter as accurate as possible!

UPDATE: I have removed the restrictions on the Server ID field, DumaOS 4 customers can now submit server mislocations.

in qos

for BO7

share urs 

At this moment it’s very hard to play for me 😅

I shoot first and I die first so anyone can help me please 😬

Thank you all 🙏

In the video, you can clearly see the abnormal behavior — it feels like hit registration and responsiveness are completely off, even though my connection appears stable. I've already tried multiple solutions, including router configuration, port forwarding, prioritizing traffic, and even using different ISPs or network setups. I'd really appreciate it if someone with more experience could take a look and give me advice or ideas on what might be going wrong. Any suggestions or insights are welcome. Thank you in advance for your help!

So recently, I noticed this error "Networking failed to start [Reason: HUENEME - NEGEV]" everytime I try to lunch this game.

I tried everything to resolve this issue by rebooting router, re-installing game, resetting network adapter, updating DNS settings etc. etc.

I finally tried deleting my PC from Geo-Filter and to my surprise, the game was able to connect to the COD servers and was all good.

When I re-added my PC to Geo-Filter, and again, the same error message pops-up. 

So, now I cant use Geo-Filter at all, without getting this error and I cant get into the game.

Also, I've put my PC as a PlayStation device and not as a PC device. (If I put my PC as a PC device itself, then Geo-Filter doesnt detect it at all, which is a whole different issue I had raised long ago.)

So my R3 is completely useless as its main feature itself is causing this issue.

Are guys at Netduma aware of this issue? Are there any fixes being worked on?