Jump to content

East

Members
  • Content Count

    95
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    East reacted to GHOST-1-EC in What is the optimal figure for High Priority Packets on both the download and upload side?   
    Using my laptop connected via wifi to my isp modem/router i bridge my ethernet and wifi connections on the laptop..... then connect the ps4 to the laptop via ethernet cable. 
    It will look like this
    1. Isp Modem/Router > Laptop (via wifi) 
    2. Laptop - wifi + ethernet connections bridged (this is done in the network adapter settings) on the laptop
    3. Laptop > Ps4 (via ethernet using the bridged connection) 
    4. Open wireshark on the laptop and launch the game - filter for udp ports in wireshark to see gaming packets specifically. 
    You'll find several tutorial videos on youtube, use the one that you understand the easiest - its an easy process once you get into it. 
  2. Like
    East reacted to GHOST-1-EC in What is the optimal figure for High Priority Packets on both the download and upload side?   
    My interest is only for game traffic.........all other traffic is insignificant for me as i dont have any issues with Nat or Connecting to lobbies or individual players. 
    Also Cod only uses UDP protocol once the match starts. 
    I have checked for the TCP protocol / packets and it is never linked to the actual game server or my ip / 3074 port (once the match starts). 
    In any event TCP priority is not advised for gaming as it causes delays / latency - it operates in total opposite to the UDP protocol, thus in COD for example it is only the udp packets that are visible in communication between the ps4 and the game server. 
    I am not certain if its the same for PC or Xbox tho. 
    I just blanked it off regardless 😁
  3. Like
    East reacted to Zippy in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Ive tried IPv6. But im on the Xbox One X. Not sure what your playing on. I personally like IPv6. The last few months Xbox Live has sent out a few updates that are really pushing IPV6. The only problem is DumaOS doesn't fully support IPV6..   And even the XR500 doesn't give one full control of it either. We would need a good firmware update to get that on board. But give it a try and experiment a bit would be my suggestion. I personally want IPV6.. 
    By disabling Share Excess you are basically locking your devices on the flower to hard bandwidth limits. Meaning they wont change even if other devices are not using anything. I feel it helps to stabilize my connection better by keeping the bandwidth consistent.. Again experiment with it and see what works best for you..
    Zippy.
  4. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    To be honest the difference ins't massive but definitely difference from my normal settings. 
    Same has OP instructed.
     
    Any ports forwarded, upnp on or off? No
    Any DMZ for console Yes
    Bufferbloat sliders enabled? make it 100% and select Never
    QoS enabled in bufferbloat section?
    Excess bandwith enabled/disabled? Unchecked
    Down/Up speed in MB reserved for gaming device in bandwidth flower? left mine has default. since I dont have much devices on it. 
    Priority rules created and port no.s? TCP, UDP or both? I used both noticed no difference then used both worked for me, yet to try UDP only
    DumaOS classified games enabled/disabled? Disabled 
     
    Im try gonna tweak other settings and see how things go.....
     
  5. Like
    East got a reaction from Grafti in Traffic Prioritization Settings: Modern Warefare (BO4)   
    This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable.   It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers.  The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. 
    The information provided to you is not a final on the research presented so far.  Furthermore, testing is ongoing.  It take this community as a whole to help gather more data/input to determine what works and what doesn't.  Please keep that in mind when reading this thread.  Thanks
    Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread:
    1. Reboot modem.  Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st).
    2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip.  If private more then likely you have double nat.  In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to).  Afterwards you may need to reboot your modem then your router again in order for it to take effect. 
    3. For your XR router make sure you Disable DumaOS Classified Games.
    4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify.
    5. Delete all existing rules if you haven't added these before.
    6. Set Anti-Buffer Bloat settings to both 100 and set it to never.  (for me even on "Never" I'm still capped to ABB slider for up/down).  Test this to see if you notice any improvement.  If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players.  No more .5 seconds behind other players.
    7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number).  Make sure that port corresponds with your console and not some other device.  It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so.  I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 
    8. Adjust Bandwidth Allocation as needed.
    9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp.
    Source 3074-3075  -> Destination 3100-3500
    Source 3100 - 3500 -> Destination 3074 - 3075 
    Source 3074-3075 -> Destination 30000-45000
    Source 30000-45000 -> Destination 3074-3075
     
    Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules.  And make sure that the port for your console shows up in Upnp.  If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding.  
    Thanks to @kinel, @GHOST-1-EC and others for the research.
     
     
    Example (Best k/d yet for me):

     

     
    Disclaimer:
    This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience.  If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you.  These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc.
     
  6. Like
    East got a reaction from Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Seye
    Ok, I've played a few rounds in MW, several different maps and must say that UDP does indeed work well instead of both. 
     

  7. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Hey like I said TCP okay at the time it felt better than my current setup before using yours on here, TCP and UDP didn't noticed a thing or difference felt like I didnt use Traffic Prioritization at all like it was OFF.
    Then UDP only:
    #Find Lobby's with in seconds of search both Multiplayer and Blackout
    #Start game with team mates, not the last person to load into the lobby while count down starts, even if I back out of a lobby and join another I'm not randomly thrown into another lobby where people have abandoned halfway to the end or about to end.
    #On blackout Alcatraz I'm most times the first 1 or 5th person to land before others depending on how close the game spawns me to the closet building 90% I'm 1 or 2nd among my team mates, I know this because I can tell when my team mate land or an enemy near by.
    #on Multiplayer and Blackout I dont miss a shot anymore, I use to spray and pray hoping first few shot I miss and the rest I hit my target.
    But now all my shots I land hit there target , Its more precise that's the only I can explain it. Movement is way quicker I'm one step ahead of my opponent unless they know I'm round the corner and even at that I still get a drop on them if Im really quick.
    No more shoot first and die first BS which I'm so happy about, now I think I would give Modern warfare try. At least now I know for sure I hit my targets!
    You can see all this in action in the videos I posted above heck Iat times I cant keep up with the pace of my character.
    I just hope other people get this working for them.

  8. Sad
    East reacted to blackfirehawk in Traffic Prioritization Settings: Modern Warefare (BO4)   
    i tryet setting rules different...
    i thought the netduma might be have a problem with big ranges .. for example
    start 3074 dest 1-65535.. but that dosnt feel good.. it prio.. but the gameplay itself dosnt feels like its prio
     
    start 3074 dest 30000-45000 feels better
     
    so i thought maybe the ranges should be smaller.. so i have made more rules ... 30000-31000... 31001-32000 and so on... from 30000 till 45000
    after that.. the prio light bulp dosnt go on.. but i see the prio pakets increase in number
     
    after that i have the feeling the games feels slower.. and the enemys are slower.. dont reakt that fast.. overall a better feeling / hitdetection
     
     
    Is there maybe a bug that the netduma only prio 1 port per range? That would explain why 1-65535 didnt work
     
     
     
     

  9. Haha
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Yeah all thanks to you,
    Just look at the second guy I turned on LOL its like I ran on  the wall like Neo in Matrix movie 🤣🤣🤣
     
     
  10. Like
    East got a reaction from Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    @Seye
    Looks like you got it figured out. 
  11. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    One of games I played
  12. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Update: So I have tried TCP which at first was good then tried UDP & TCP made no difference, thentl UDP only boy oh boy......the difference is clear my gamplay smooth and much more better.
    Servers and peers I connected to ping where between  5 to 8ms, in game ping was between 18 to 23 steady.
    I would say to anyone else who wants to try this out and ain't getting results, I would suggest trying UDP only.
    @East  Thanks for sharing this.


  13. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    It does for me
  14. Like
    East reacted to Netduma Fraser in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Anti-Bufferbloat is not a feature to fine tune the CoD experience, it exists to eliminate local congestion which is what it does. Traffic Prioritization prioritizes ports/packets to eliminate jitter/spikes and does this automatically. These are what we recommend to use but everyones connections are different which is why we suggest that people experiment to see what works for them which is what's happening in this topic which is great. Bagsta the other day posted a video of his game the other day with good connection and he used our recommended settings so I don't think we need to chime in really as experimentation is down to the customer themselves to tailor to their specific connection, of course we'll help where possible.
  15. Like
    East reacted to PUBzZz in Traffic Prioritization Settings: Modern Warefare (BO4)   
    We need the Duma Dev's to chime in at this point.  I know they busy with 3.0 but I think we need to address why one of the key features of the Duma "Anti Bufferbloat" seems to do more harm than good with MW. Also maybe the Dev's can gives us a detailed list of what they see MW doing port wise for PS/Xbox/PC.  
    I can say since I stopped using the Anti Bufferbloat and prioritized those port ranges the game plays much better hit detection wise.  I'm a little mind blown in the difference.  
     
  16. Like
    East reacted to Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Yeah Lobby doesn't reach 100 players more like 38 then the game deploys.
    I noticed I have 40 when deployed, does that mean I'm in a lobby with 40 players? Even if I quit the game when deployed search another lobby it's the same 40 players then the game start.
    So far what I have noticed:
    1.Hit detection has NEVER been this good ever since I have used Netduma R1. Yes I do get good detection like 1 good lobby in every 5 games which is at random but with this rules it's consistent Evey game I played so far 3 in total.
    2.My reaction time has improved, Cant explain it best way I can describe this it feels like I'm playing on LAN party with friends in the same room.
    I just played 3 games after making changes as its late here and I got work the next morning will post more results here tomorrow
    Here was my last game watch the clip, I could easily tell if I missed a shot. I didn't miss one shot. Most times I just spray lol
     
     
    Not ready to conclude just yet but so far there's been a major difference using method one, I plan to grind over the weekend and give you my final verdict. Thanks for sharing your settings.
  17. Like
    East got a reaction from Hydros85 in Traffic Prioritization Settings: Modern Warefare (BO4)   
    This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable.   It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers.  The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. 
    The information provided to you is not a final on the research presented so far.  Furthermore, testing is ongoing.  It take this community as a whole to help gather more data/input to determine what works and what doesn't.  Please keep that in mind when reading this thread.  Thanks
    Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread:
    1. Reboot modem.  Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st).
    2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip.  If private more then likely you have double nat.  In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to).  Afterwards you may need to reboot your modem then your router again in order for it to take effect. 
    3. For your XR router make sure you Disable DumaOS Classified Games.
    4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify.
    5. Delete all existing rules if you haven't added these before.
    6. Set Anti-Buffer Bloat settings to both 100 and set it to never.  (for me even on "Never" I'm still capped to ABB slider for up/down).  Test this to see if you notice any improvement.  If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players.  No more .5 seconds behind other players.
    7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number).  Make sure that port corresponds with your console and not some other device.  It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so.  I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 
    8. Adjust Bandwidth Allocation as needed.
    9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp.
    Source 3074-3075  -> Destination 3100-3500
    Source 3100 - 3500 -> Destination 3074 - 3075 
    Source 3074-3075 -> Destination 30000-45000
    Source 30000-45000 -> Destination 3074-3075
     
    Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules.  And make sure that the port for your console shows up in Upnp.  If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding.  
    Thanks to @kinel, @GHOST-1-EC and others for the research.
     
     
    Example (Best k/d yet for me):

     

     
    Disclaimer:
    This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience.  If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you.  These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc.
     
  18. Like
    East got a reaction from Seye in Traffic Prioritization Settings: Modern Warefare (BO4)   
    For me in Modern warfare when one match ended it was modest delay before searching for another match.  Now it's almost instant and I see users populating.  So I know what you are talking about.  But I didn't notice that until I added ports from the 3000 range. I assume some of them are tcp from talks in the other thread in the OP.
    What exactly was a significant difference using TCP? It is strange that you didn't get the same results from both udp/tcp vs just tcp.  Shouldn't both work for just tcp if tcp is required for that port?   BTW thanks for the follow up.
     
  19. Like
    East reacted to kinel in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Thers 4 rules you need to make east poted above but i will again
    Rule 1  source 3074-3075 destination 30000-45000  udp
    Rule 2  source 30000-45000  destination 3074-3075 udp
    Rule 3  source 3074-3075  destination 3100-3500  udp
    Rule 4  source 3100-3500  destination 3074-3075 udp
    This is how i recomend you do it
    sorry i made a mistake here but i just fixed it
  20. Like
    East got a reaction from GHOST-1-EC in Traffic Prioritization Settings: Modern Warefare (BO4)   
    This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable.   It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers.  The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. 
    The information provided to you is not a final on the research presented so far.  Furthermore, testing is ongoing.  It take this community as a whole to help gather more data/input to determine what works and what doesn't.  Please keep that in mind when reading this thread.  Thanks
    Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread:
    1. Reboot modem.  Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st).
    2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip.  If private more then likely you have double nat.  In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to).  Afterwards you may need to reboot your modem then your router again in order for it to take effect. 
    3. For your XR router make sure you Disable DumaOS Classified Games.
    4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify.
    5. Delete all existing rules if you haven't added these before.
    6. Set Anti-Buffer Bloat settings to both 100 and set it to never.  (for me even on "Never" I'm still capped to ABB slider for up/down).  Test this to see if you notice any improvement.  If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players.  No more .5 seconds behind other players.
    7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number).  Make sure that port corresponds with your console and not some other device.  It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so.  I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 
    8. Adjust Bandwidth Allocation as needed.
    9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp.
    Source 3074-3075  -> Destination 3100-3500
    Source 3100 - 3500 -> Destination 3074 - 3075 
    Source 3074-3075 -> Destination 30000-45000
    Source 30000-45000 -> Destination 3074-3075
     
    Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules.  And make sure that the port for your console shows up in Upnp.  If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding.  
    Thanks to @kinel, @GHOST-1-EC and others for the research.
     
     
    Example (Best k/d yet for me):

     

     
    Disclaimer:
    This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience.  If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you.  These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc.
     
  21. Like
    East got a reaction from DanyKTM in Traffic Prioritization Settings: Modern Warefare (BO4)   
    This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable.   It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers.  The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. 
    The information provided to you is not a final on the research presented so far.  Furthermore, testing is ongoing.  It take this community as a whole to help gather more data/input to determine what works and what doesn't.  Please keep that in mind when reading this thread.  Thanks
    Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread:
    1. Reboot modem.  Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st).
    2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip.  If private more then likely you have double nat.  In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to).  Afterwards you may need to reboot your modem then your router again in order for it to take effect. 
    3. For your XR router make sure you Disable DumaOS Classified Games.
    4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify.
    5. Delete all existing rules if you haven't added these before.
    6. Set Anti-Buffer Bloat settings to both 100 and set it to never.  (for me even on "Never" I'm still capped to ABB slider for up/down).  Test this to see if you notice any improvement.  If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players.  No more .5 seconds behind other players.
    7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number).  Make sure that port corresponds with your console and not some other device.  It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so.  I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 
    8. Adjust Bandwidth Allocation as needed.
    9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp.
    Source 3074-3075  -> Destination 3100-3500
    Source 3100 - 3500 -> Destination 3074 - 3075 
    Source 3074-3075 -> Destination 30000-45000
    Source 30000-45000 -> Destination 3074-3075
     
    Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules.  And make sure that the port for your console shows up in Upnp.  If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding.  
    Thanks to @kinel, @GHOST-1-EC and others for the research.
     
     
    Example (Best k/d yet for me):

     

     
    Disclaimer:
    This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience.  If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you.  These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc.
     
  22. Like
    East reacted to Zippy in Traffic Prioritization Settings: Modern Warefare (BO4)   
    No worries. Seems like we are on the same sheet of music! Good to see there is something somewhat consistent about this.. lol.. We share the same thoughts and settings! 👍
    Zippy.
  23. Like
    East got a reaction from Zippy in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Exactly what I did.  Thanks for clarifying that.
     
  24. Like
    East reacted to Zippy in Traffic Prioritization Settings: Modern Warefare (BO4)   
    Rodney, I would start high with your sliders then work your way down. If you over buffer your connection that also seems to have a negative effect.  Personally I rarely use buffer Bloat Control. Or if I do use it I set my sliders very high. Like 98% up and down..
    Zippy.
  25. Like
    East reacted to Rodney Rosado3 in Traffic Prioritization Settings: Modern Warefare (BO4)   
    I turn anti bufferbloat off feels bit better 
×
×
  • Create New...