DumaGuy2021

I think it's a bit far fetched, at least that influencing speed and hitreg is done on purpose.
 
Is the game rigged? Well yes. If you haven't played for say a month and you play your first game you will stomp the enemy no problem as the game's matchmaking algo is reset. Then after a few games it ups the ante until you start doing average.
 
Matchmaking this way induces several issues, one is that it takes longer to match up and the other that the higher skilled playerpool is geographically more diverse, so you get a lot more latency variation. That also means that you will see more issues with hit registration as the server applies it's latency balancing system more aggressively. I have tested this in the past playing on the same server, where sometimes you would get hitmarkers in 1-2 frames and other times in 4-5 frames, ie sometimes it took 66ms to get a hitmarker on a 40ms server while other times it took 133ms to get a hitmarker. 
 
The whole issue with CoD is that it is inherently a very low skill game, possibly the lowest skill game on the market, at least the last few iterations after the advanced movement era. if you pay attention to positioning and your angles you can easily find success. If you consider skill as a bell curve, most seasoned players will be slightly to the right of the mean distribution. That means there is a large group that is only slightly above average. If you would match randomly, there is a good chance that you have a lot more success as you can beat them on raw skill, ie play more offensive without regard to positioning etc. This goes away when EOMM/SBMM is tightened as now it's forcing you into that style.
 
There is also the perception. If you play bots you would not notice the variation in hit registration much as you win the gunfight anyway. But if you are in your own skill group, you face players that react just as fast and employ the same tactics as you would so it magnifies the situations where you think you should have won the fight but you didn't. Because the other guy might have been slightly faster but it didn't show on your screen. 
 
If you are in the slightly above average group you will also find people with better equipment, scuf controllers, better routers, playiing on monitors etc.  

They implemented some measures to stop people forcing servers by changing some file, but that's not really what Geo-filter does so you should still be fine. Give it a go and let us know how you get on, we've been playing a little in the office recently and it seemed fine.

Je crée ce topic dans l'intention d'aider certaines personnes qui galère avec leurs routeurs ou voir même avec leurs réseaux, par respect pour ce forum et les membres de netduma je ne citerais pas le nom de la concurrence  donc les questions du genre "c'est quoi ton routeur" ou autre du même type a éviter svp..Ce topic a pour but de vous orienter vers les bonnes pistes sans pour autant vous mâché le travail je ne suis pas un ingénieurs réseau mais un passionné qui hésite pas a partager si besoin...
1---> LATENCE/GIGUE
RTT ou RTD (Round-Trip Time ou Round-Trip Delay)
Il s'agit du délai exprimé en ms dans la réponse au Ping. Ce délai indique le temps mis par le packet pour atteindre sa destination et revenir.
Au plus ce délai est proche de 0, au plus la qualité de la connexion est bonne.

TTL (Time To Live)
Il s'agit de la durée de vie du paquet transmis. Lors du trajet du paquet, une valeur est décrémentée à chaque traversée d'un routeur. Cela permet non seulement de connaître le nombre de noeuds réseau traversés mais aussi d'éviter qu'un paquet tourne en boucle.

Lag ou latence
C'est le délai mis par un paquet pour atteindre sa destination. Par abus de langage, on parle du temps de latence lors du résultat en ms du ping mais ce temps correspond en réalité à la moitié de la valeur RTT.
Même avec un débit (bande passante) élevé, un temps de latence élevé détériore grandement la qualité d'un réseau et la perception que peut en avoir l'utilisateur.

Gigue (Jitter en Anglais)
c'est une notion un peu plus compliquée car il s'agit de la variation du temps de latence. Au plus la gigue est proche de 0, au plus le temps de latence a la même valeur et est donc stable.
Une gigue élevée, même avec un temps de latence faible, perturbe les protocoles en temps réel : Gaming,Téléphonie IP, Bureau virtuel (Cloud), etc...

Recommandations
Afin d'avoir la meilleure qualité de connexion possible, vous devez :
-Avoir un débit élevé (fibre)
- Avoir un temps de latence le plus proche possible de 0,
- Avoir une gigue la plus proche possible de 0.

Ces vérifications sont à effectuer régulièrement sur votre réseau Internet, surtout lorsque vous remarquez des lenteurs sur la connexion Internet.
Lien pour comprendre comment tester son RTT---> https://fr.linkedin.com/learning/l-essentiel-de-wireshark/evaluer-et-grapher-la-latence


2--->L'ORDRE DES TRAITEMENTS APPLIQUÉS PAR LE FIREWALL
Comprendre l'ordre dans lequel les règles de NAT et de filtrage sont appliquées est important lorsque l'on configure son firewall.
Ici comme exemple on s'appuiera sur iptables (linux).
Il existe 5 chains dans la table ip (Prerouting, Input, Forward, Output, Postrouting) et 3 tables principale (Filter, Nat, Mangle) et chaque table a des règles différentes chaque chains vous donne la possibilité d'agir sur le paquet (faite vos recherches sur internet pour savoir a quoi correspondent ces chains).
Il est important de connaitre l'ordre dans lequel la chains est appelé pour chaque table, et connaitre également l'ordre de traversé de la chains.
Chaque routeur a sa manière de procédé a vous de vous renseigner..


 
3---> PRIORISATION DE TRAFFIC
Pour la mise en place de la priorisation de trafic,(pour ma part) il faut configurer d'un côté des queues (file d'attente) et de l'autre des rules (règles d'affectation des paquets dans ces files d'attente)
-Queues : "file d'attente" à laquelle est associée une priorité de traitement et une bande passante
 -Rules : "règle d'affectation" définissant la queue par laquelle un paquet va transiter. Ces règles sont les mêmes que pour la configuration du firewall : filtrage par port et adresse IP source, port et adresse IP de destination, protocole utilisé, etc...
*La priorité de traitement la plus forte doit toujours être donnée aux applications nécessitant un traitement en temps-réel. Typiquement, la VoIP ou Gaming.
*La priorité suivante doit toujours être donnée aux acquittements TCP (ACK). Les ACK correspondent à des sortes d'accusé de réception sur les données transmises en TCP. Il est important que ces paquets soient prioritaires car autrement l'émetteur considérera que les paquets envoyés n'ont pas été correctement reçus et procédera à leur réémissions. Ce qui, par effet boule de neige, augmentera la charge sur la ligne Internet.
Comme pour le (2) la configuration dépend du routeur...
Pour moi c'est les 3 points primordiale pour commencer après ont peu pousser le vice encore plus loin..je tient a souligné quand même que je dispose que d'un routeur et d'un switch des plus banale,pas d'equipemment de la nasa comme certain sur ce forum et une connexion du feu de dieu..j'espère que ça pourra aider plus d'un.

To bypass that open the google drive link, make sure you are signed in and next to your profile icon on the top right, hit the 3 dots, and star the caddy redbull file. Go to your google drive, recent tab. right click redbull caddy that you starred and make a copy. Then download the copy and it should work! 

ive made a few threads about this topic updated for coldwar
This is all thanks to a7legit who told me about it  who sadly passed away
on the forums but i wanted to update it  here to make it less confusing
Honestly guys you should read  some of the info on this thread below from the forum users here its very intresting and helps a lot
 here is a link to the poll i created over a year ago if you found this helpful please vote here
when playing cod mw19 now its coldwar
the game uses 3 ports all the time
 
the two ways i know of how you find out what ports the game uses for you are
the first is a programe called wireshark on pc
the second is in the older firmware called network monitor
but it isnt in the new firware
It shows you the ports your connected to  when gaming 
This to me is brilliant  for every game
 
 i ave found a load of ports the game uses  in a list below
if you put these ports in to traffic priortizatio your hit registration becomes brilliant
before i was struggleing to get kills now when i put the ports in before it would take a whole magazine to kil on person   now two or three bullets kill them easily
when you put the right ports in the game it is using you can istantly tell
the three ports go like this
the first is always 3074 for myself on ps xbox1 is 3075 i think
this is the  port i wil call it  this stays the same for me it never changes
 
the second ports changes everytime you restart the game for me that is
I wil call it data centre server port to make it easier to understand
 
the 3rd is the most important port . this changes every time you join a new game lobby
this port as soon as i put this main  port i will call it in  my hit detection becomes brilliant
 
heres an egxample i start the game without putting in the main port in
  I playing and im struggling to get kills i quickly run to my pc put the port number in  while im stil playing in the same lobby
 as soon as i put them in trafic priortization imy hit registration becomes brilliant and i  aint struggling no more
 This is the same game after game so i know its no placebo affect  ive did the same thing on previous cods as well with same results  
 
these are the ports i found so far playing cod  coldwar and mw19
 
i put these into traffic priortizatin in single rules
i prefer to do them indavidually as i know what ports the game is using for me   
The game uses only 3 ports at once
 for you guys who are not using the older firmware you have to open them up in ranges
 
some of these ports might be listed twice as i havent had time time edit the list 
 
 
30190    30500  30600   30020   30030   30070
30040  30080   30110   
30410     30350   
30550 30520 30130 30060  30060   30100  30070  30010  30020
30920    30970  30410  30140    30090    30020    30160  30230
30080    30090  30100  30940  30160  30060  30040  30310    
30120    30070    30020  30080  30040  30140  30310
31350   31930   31030  31080    31300   31350
32850
32790    32960  32730    32400  32450  32540  32570   32580
32590   32550  32460   32490   32550  32580  32310 32560
32680    32310   32350   32930  32540  32700  32710  32650
33670   33980  33420   33420    
33640
34790  34790  34260
34130  34020    34800    34070    
35310   35710      35300 35530
35800  35660    35710     35300   35320      35800
36570    36440  36440    36280 36700  36670  36360
36360    36280  36800   36050   36290  36930
37290    37260  37890    37000   37580  37620    37160
38160    38890    38280  
39300   39550   39500   39860     
40110   40280  40510   40820   40990
41640    41620    41100
42130     42200   42510  42160   42420 
 43350    43380    43610  43840  43300  
44800  44470    44820  44280  44640  44110
44660  44790              
3074    
9308    
you can put these ports into ranges
this is how i would wright the ranges but im no expert at
it in the link a form user called  RL327 shows how to do this propely as i leared this stuff from him
HERE IS THE NEW UPDATED  PORTS YOU NEED FOR COLDWAR THIS WAS TESTED ON PS4
 Rule1Source  3074-3076 destination  30000-45000 udp  rule 1
 Rule2 Source 50000 -65535   destination   3074 -3076 tcp  only
 This is in traffic priortization
  You will know if its working  when your infame  these rules will show as rdd in the traffic priortization screen
These are the only 2 rules you need in my opinion atm for coldwar
please can you vote in the  link above if this helped you at all
also the link has a better info in it from other users here
With a bit more details
as im trying to get theadmins to reinstall the ole network monitor
 as the new network monitor dosent have this feature
and i wouldnt have been able to post these ports if i downgraed to the older firmware
 
 
 

The fix to nrmp flash not working is to immediately spam the command again, so it will fail or give a tftp request error, immediately enter the command again, I copy and paste. Have you tried using these commands: nmrpflash -i net10 -f XR300-V1.0.3.34_10.3.27.chk Replace the firmware name with whatever file you are using. But it will say timeout something and just immediately copy and paste the command again, be quick. Always works for me when I am switching between firmwares like tomato to dumaos etc. As always with firmware updating, have nothing connected to the router except powerbank obviously, and your computer connected to the router in lan port 1, not wan port. Then set yourself a static ip address as well as a dns even though the dns server isn't necessary and try again. This is another command you can try, as always, replace the chk with the name of your firmware: nmrpflash -v -i net10 -f XR300-V1.0.3.34_10.3.27.chk -t 10000 -T 10000 -A 192.168.1.1 -a 192.168.1.1 . If you changed your gateway address from 192.168.1.1 to another, then replace that as well.  Edit: I didn't read that you have solved your issue but I will leave this up incase this can help anyone else!

I think he is talking about the reset distribution in the bandwidth allocation tab. Simjc said something about pressing reset as well. Also if you want to try this method out, reset distribution for upload and also click reset distribution for the download as well, as the settings are completely separate from another.

I did notice an improvement with hit registration resetting bandwidth allocation but didn't do it individual like upload and download, I would try that next. I just played about two games, but I would do more testing.
 
 
This is a test video, there are other clips too but just to show the hit registration is great. Like I said I played just two games last night but I would be doing more test and sharing my findings on here.
Same settings I posted above, but I added my PS5 to Traffic Prioritization. If you interested.

-ps4
-Geo off
-60/60 cc always on (a+ dlsreports with no yellow or red above measurements or big jitter spikes)
-upnp
-wired
-3074 src 30000-45000 dst tp
I remember A7Legit saying something about hitting the reset button before every match once you had the sliders optimized and for some reason it works, dont know what it does exact;y, but it improves hit detection, if i dont hit reset distribution they sponge my bullets taking nearly a full magazie to kill. Thought it was a placebo but it works everytime.

Hey duma Family! I thought it would be nice to idea we all share our settings that works for each of us, for Call of duty Modern warfare, Cold War and Warzone. So if anyone wants to try out other settings it would be available in one place.
Here is mine....
Console:PS5
Geo-Filter Settings:
Filter Mode & Strick Mode :enabled
Distance : 1000 , Ping: 0
Congestion Control 
Always - 77/81
Traffic Prioritizations - DumaOS Classified Games enabled
Lastly I put my PS5 into DMZ zone to have OPEN Nat type, port forwarding doesn't really work.