how to get better hit detection

[SolidOny]

29 minutes ago, CRarsenxL said:

Try it. That’s the best one I found. Idk y ppl say Src should be 1-65535, to me it’s the opposite. 

 

Ive made money playing this game and linked my profile above. See for yourself if you think I’m kidding 

You think having UPNP on or off ? 

[CRarsenxL]

4 hours ago, SolidOny said:

You think having UPNP on or off ? 

Doesn’t matteR if UPNP or pf. I found DMZ feels super off however 

[chatmandu]

6 hours ago, TODDzillaInLA said:

the source port will never be random if you have a router like netduma where you force the port to use only 1 port, not opening all the ports up across the board 

Wrong. 

Port forwarding opens up the destination port on your firewall. It will allow connections from any source port to that destination port. I can't believe you're still struggling with something so basic, but running your mouth as if you're educated. 

QoS is completely separate configuration from port forwarding - but you're prioritising the inbound traffic, that's been permitted by the port forwarding, and the outbound traffic originating on your gaming device. 

"get off the forum then instead of giving bad advice..."

Quite. 

NetdumaOS only has one rule that is supposed to match both inbound and outbound traffic. I'll say it again:

Protocol = UDP/TCP

Destination port = 3074

Source port = any 

Class = gaming/voice

That should be all you need, unless NetdumaOS is badly programmed and they've got their source and destination ports programmed in reverse. 

 

 

 

[TODDzillaInLA]

49 minutes ago, CRarsenxL said:

Doesn’t matteR if UPNP or pf. I found DMZ feels super off however 

if you want to optimize your connection for warzone turn upnp off, you dont want other devices uses ports while your playing

[TODDzillaInLA]

31 minutes ago, chatmandu said:

Wrong. 

Port forwarding opens up the destination port on your firewall. It will allow connections from any source port to that destination port. I can't believe you're still struggling with something so basic, but running your mouth as if you're educated. 

QoS is completely separate configuration from port forwarding - but you're prioritising the inbound traffic, that's been permitted by the port forwarding, and the outbound traffic originating on your gaming device. 

"get off the forum then instead of giving bad advice..."

Quite. 

NetdumaOS only has one rule that is supposed to match both inbound and outbound traffic. I'll say it again:

Protocol = UDP/TCP

Destination port = 3074

Source port = any 

Class = gaming/voice

That should be all you need, unless NetdumaOS is badly programmed and they've got their source and destination ports programmed in reverse. 

 

 

 

k

[Newfie]

Let’s keep it friendly, it’s a great thread where everyone is helping each other and by doing so everyone benefits with a better online experience which makes this community stand above all others.
 

 

[Nalsano_]

7 hours ago, chatmandu said:

Tort. 

La redirection de port ouvre le port de destination sur votre pare-feu. Il autorisera les connexions de n'importe quel port source à ce port de destination. Je ne peux pas croire que vous luttez toujours avec quelque chose d'aussi basique, mais que vous courez la bouche comme si vous étiez instruit. 

La qualité de service est une configuration complètement distincte de la redirection de port - mais vous donnez la priorité au trafic entrant, qui a été autorisé par la redirection de port, et au trafic sortant provenant de votre appareil de jeu. 

"sortez du forum alors au lieu de donner de mauvais conseils..."

Assez. 

NetdumaOS n'a qu'une seule règle censée correspondre à la fois au trafic entrant et sortant. je le répète :

Protocole = UDP/TCP

Port de destination = 3074

Port source = n'importe lequel 

Classe = jeu/voix

Cela devrait être tout ce dont vous avez besoin, à moins que NetdumaOS ne soit mal programmé et qu'ils aient leurs ports source et destination programmés à l'envers. 

 

 

 

Wrong information on a router under duma os if you put example 1-65535 in source and 3074 in destination it will not work !!

[chatmandu]

12 hours ago, CRarsenxL said:

Try it. That’s the best one I found. Idk y ppl say Src should be 1-65535, to me it’s the opposite. 

 

Ive made money playing this game and linked my profile above. See for yourself if you think I’m kidding 

I've performed a fresh wireshark capture and this is what I've found.

The game traffic connection is initiated by the CoD server inbound to the gaming device. 

The destination port internally is 3074 and the source port (internet) is random. 

The gaming device responds using the same ports. 

 

On a 'normal' router (e.g. Cisco), you would need two rules for QoS

Outbound packets from gaming device to CoD server.

Source IP = gaming device

Source Port = 3074

Destination IP = 'any'

Destination port = 'any'

 

Inbound packets from CoD server to your gaming device. 

Source IP = any

Source port = any

Destination IP = gaming device

Destination port = 3074

 

DumaOS doesn't allow you to specify the source and destination IPs for the QoS rules, so it isn't clear how the rules are applied. 

You may be correct that Source port = 3074 and Destination port = 1:65535 works best with DumaOS. 

This is what I previously configured on my Asus router and the packets were correctly marked: 

 

[Bert]

Different router brands have different notations for this. Some other let you specify both inbound and outbound separately and some always assume source to be the sender. DumaOS combines both directions but in reality inbounds means forwarding incoming WAN traffic to LAN and vice versa. On more professional systems you would add a rule to the WAN interface SRC 3074 DST 30000-45000 and Ethernet interface SRC 30000-45000 DST 3074. The rule is always applied to sending traffic since the interface can not control the receiving side. Ie you can not control what you will receive over the internet.
 

also it’s really simple to check if you’re rule is actually working. Look at the packet counter, for games WW2 and later it should add 60 packets under ‘prioritized’ for every second you play the game, both inbound and outbound. Unless it’s private games they have different tickrates in a lot of cases.

 

TCP is only used for communication to the back end servers, uploading stats etc so doesn’t affect your gameplay.

[chatmandu]

1 hour ago, Locosano said:

Wrong information on a router under duma os if you put example 1-65535 in source and 3074 in destination it will not work !!

Won't that mean that you can't prioritise updates from the game server? My wireshark capture shows that inbound updates have destination port 3074 and source port 'any'. 

The inbound traffic will be fighting for internal network priority with other traffic - e.g. Netflix, which is downloaded in 'chunks' rather than 'streamed'. 

[Bert]

3 minutes ago, chatmandu said:

Won't that mean that you can't prioritise updates from the game server? My wireshark capture shows that inbound updates have destination port 3074 and source port 'any'. 

The inbound traffic will be fighting for internal network priority with other traffic - e.g. Netflix, which is downloaded in 'chunks' rather than 'streamed'. 

 

If you look at your Wireshark captures you will probably find that the outgoing packets have destination and ports reversed.

 

So when you make a rule in DumaOS saying:

PS4

source 3074-3074

destination 1-65535

 

it makes 2 ques:

ETH:

source 1-65535 any IP

destination 3074-3074 PS4 IP

 

WAN1:

Source 3074 PS4 IP

destination 1-65535 any IP

 

It’s just to simplify the setup. You could say source in DumaOS is equal to local host in Asus.

[Nalsano_]

14 minutes ago, chatmandu said:

Won't that mean that you can't prioritise updates from the game server? My wireshark capture shows that inbound updates have destination port 3074 and source port 'any'. 

The inbound traffic will be fighting for internal network priority with other traffic - e.g. Netflix, which is downloaded in 'chunks' rather than 'streamed'. 

 

Interesting I think that asus or other company that makes so-called "gaming" router are really efficient unfortunately the qos of duma os is very wobbly nobody manages to have 1 or 2 ms of bufferbloat with a router of the xr range so I imagine that the priority traffic is also wobbly ...

[Netduma Fraser]

You should be able to get that minimal level of bufferbloat if you really dial in your settings. Don't use Benchmark for that as we're still improving it. If you saturate your connection with downloads etc and experiment with percentages to see what lowers it the most you should be able to get it http://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping

[Bert]

CoDeL manages latency across the ques. It works really well but also it’s very CPU intensive. There is no routers that I know of for home use that can do this at gigabit speed. This is because it requires the configuration of many traffic classes, and different priority weights.

Downside of codel is that it increases absolute latency a little bit over other forms like PFIFO.

 

It also depends on how you measure. Like DSL reports measures latency by sending http GET requests. Not ICMP ping. This sort of traffic is exactly what CoDeL is meant to optimize. Whereas the XR routers use PFIFO and say you have gaming traffic optimized, it won,t do anything to these GET requests. But QoS does work when you’re actually gaming.

 

I have never tried it but possibly if you configure your XR router for that type of traffic you will see a improvement in bufferbloat ratings. It doesn’t necessarily produce real world results though.

 

That said, CoDeL is the better option for all round general use if you have the CPU power to run it.

[chatmandu]

1 hour ago, Locosano said:

Interesting I think that asus or other company that makes so-called "gaming" router are really efficient unfortunately the qos of duma os is very wobbly nobody manages to have 1 or 2 ms of bufferbloat with a router of the xr range so I imagine that the priority traffic is also wobbly ...

Bufferbloat is pretty good with Asus Merlin and CakeQoS.

Unfortunately, CakeQoS isn't currently compatible with traffic shaping QoS (e.g. FlexQoS) and I still experience some lag. I purchased a DumaOS router hoping for a better experience, but it failed to deliver. 

This test was conducted with my son streaming video via a Roku device. 

[Netduma Fraser]

@chatmandu I see you haven't made a topic, if you do so we can help with whatever problem/issue you're facing

[chatmandu]

13 minutes ago, Bert said:

CoDeL manages latency across the ques. It works really well but also it’s very CPU intensive. There is no routers that I know of for home use that can do this at gigabit speed. This is because it requires the configuration of many traffic classes, and different priority weights.

Apparently the Raspberry Pi 4 can handle gigabit speeds in both directions when running OpenWRT. 

Some people have suggested that the lag spikes I'm experiencing may be due to the outdated Broadcom drivers that are used by the Asus router. 

I'm planning to buy one and will test it with my Asus router operating as an Access Point. If that works as well as people claim, I will sell my Asus router and buy a cheap access point. 

[Bert]

If you look at Amazon and other places you can often buy small cheap barebones PCs with dual network cards. Install something like Untangle or OpenWrt x86-64 and it will basicly blow every residential or gaming router out of the water. Then you can definitly do SQM at gigabit speed.

[CRarsenxL]

12 hours ago, chatmandu said:

Wrong. 

Port forwarding opens up the destination port on your firewall. It will allow connections from any source port to that destination port. I can't believe you're still struggling with something so basic, but running your mouth as if you're educated. 

QoS is completely separate configuration from port forwarding - but you're prioritising the inbound traffic, that's been permitted by the port forwarding, and the outbound traffic originating on your gaming device. 

"get off the forum then instead of giving bad advice..."

Quite. 

NetdumaOS only has one rule that is supposed to match both inbound and outbound traffic. I'll say it again:

Protocol = UDP/TCP

Destination port = 3074

Source port = any 

Class = gaming/voice

That should be all you need, unless NetdumaOS is badly programmed and they've got their source and destination ports programmed in reverse. 

 

 

 

The gaming/voice is only for wifi.

Normal (default) is what should be used

[CRarsenxL]

4 hours ago, Bert said:

Different router brands have different notations for this. Some other let you specify both inbound and outbound separately and some always assume source to be the sender. DumaOS combines both directions but in reality inbounds means forwarding incoming WAN traffic to LAN and vice versa. On more professional systems you would add a rule to the WAN interface SRC 3074 DST 30000-45000 and Ethernet interface SRC 30000-45000 DST 3074. The rule is always applied to sending traffic since the interface can not control the receiving side. Ie you can not control what you will receive over the internet.
 

also it’s really simple to check if you’re rule is actually working. Look at the packet counter, for games WW2 and later it should add 60 packets under ‘prioritized’ for every second you play the game, both inbound and outbound. Unless it’s private games they have different tickrates in a lot of cases.

 

TCP is only used for communication to the back end servers, uploading stats etc so doesn’t affect your gameplay.

Def doesn’t affect gameplay

[CRarsenxL]

4 hours ago, Locosano said:

Wrong information on a router under duma os if you put example 1-65535 in source and 3074 in destination it will not work !!

You need to do Src 3074 and dst any

[Nalsano_]

2 hours ago, Netduma Fraser said:

You should be able to get that minimal level of bufferbloat if you really dial in your settings. Don't use Benchmark for that as we're still improving it. If you saturate your connection with downloads etc and experiment with percentages to see what lowers it the most you should be able to get it http://support.netduma.com/en/support/solutions/articles/16000074717-how-to-test-your-internet-ping

Unfortunately fraser I had the r1 which for me had a qos which was capable of great things with the bufferbloat but duma os impossible to have a result on the bufferbloat and I tested 2 different ISPs in France "orange and sfr" both in fiber ftth 1gb down and 500 up. Unfortunately the only ones which we succeeded in giving me a bufferbloat of 1 to 2 ms were the r1 or openwrt by limiting the bitrates compared to the material ... and I find that sorry .. of have regressed compared to your first router. All my tests were done with pingplotter and dslreport at the time and the same observation .. that I lower the cursors to 90% or 20% my ping fluctuates and a feeling of delay in the games is always present the best option for me and deactivated the qos: / ..

[chatmandu]

50 minutes ago, CRarsenxL said:

The gaming/voice is only for wifi.

Normal (default) is what should be used

Why is it only for WiFi? Is that a limitation of the DumaOS?

Surely all traffic is classed as 'normal' by default and you're trying to increase the priority by classng it as gaming/voice ('expedited forwarding' would be the dscp equivalent)? If the end result is having the traffic classed as 'normal', what's the point?

[CRarsenxL]

20 minutes ago, chatmandu said:

Why is it only for WiFi? Is that a limitation of the DumaOS?

Surely all traffic is classed as 'normal' by default and you're trying to increase the priority by classng it as gaming/voice ('expedited forwarding' would be the dscp equivalent)? If the end result is having the traffic classed as 'normal', what's the point?

Fraser confirmed normal default was Ethernet and wireless type gaming voice / video was for wifi 

[Netduma Fraser]

1 hour ago, Locosano said:

Unfortunately fraser I had the r1 which for me had a qos which was capable of great things with the bufferbloat but duma os impossible to have a result on the bufferbloat and I tested 2 different ISPs in France "orange and sfr" both in fiber ftth 1gb down and 500 up. Unfortunately the only ones which we succeeded in giving me a bufferbloat of 1 to 2 ms were the r1 or openwrt by limiting the bitrates compared to the material ... and I find that sorry .. of have regressed compared to your first router. All my tests were done with pingplotter and dslreport at the time and the same observation .. that I lower the cursors to 90% or 20% my ping fluctuates and a feeling of delay in the games is always present the best option for me and deactivated the qos: / ..

I'm sure we can get down to why that is, those results should certainly still be achieved with the XR routers