chatmandu

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?

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.

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. buffer_bloat2.mp4

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'. netflix2.mp4

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:

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.

I no longer have a netduma router and can't confirm what you mean by 'turns on and off'. QoS traffic shaping rules should always be on. They only get applied to the relevant traffic, so there is absolutely no need to turn them off. If they're being automatically disabled, then it's yet another reason to ditch your router. The rules I've provided are definitely correct for CoD. I've proven this on an Asus router running FlexQoS and traffic is correctly matched and marked (according to my rules) as class 'netcontrol' and '000000' which is the highest possible priority in the FlexQoS system.

Yes. It uses destination port 3074 (confirmed via wireshark), but the source port will always be random because that's the way that IP connections work. You're clearly an idiot that continues to insult people from a position of ignorance - e.g. you're still confusing QoS with opening ports! What a clown 🤣🤡🤣.

Anybody that states a QoS rule is the equivalent to placing a device in the DMZ, and then refuses to accept their mistake, clearly knows nothing about networking. With regards to the other suggested rules that have been posted, the destination port will always be static (i.e. 3074). The source port is assigned randomly on a per connection basis. This allows the destination device to keep track of all the connections on port 3074. If you're building a QoS rule for CoD, then it should be destination port TCP/UDP 3074 and source port 'any'. That's it. End of.

A QoS rule will only be applied to traffic that matches the rules. That's why it's pointless having an 'any port to any port' rule because it will apply the QoS to all traffic. For hit registration, you only want to prioritise traffic on TCP/UDP 3074 (for PC CoD).

Lol. You're confusing port forwarding with QoS prioritisation. Applying QoS to traffic isn't opening any ports at all.

(deleted)

Yes. You're correct. I wrote that on my first day of owning a DumaOS router and I hadn't realised that there are no in/out rules. I've actually returned my router because I don't think they're delivering on their promises/hype. For those with these routers, who aren't sure what rules to use, I'd recommend disabling the Duma preconfigured QoS rules and enabling this for CoD: IP address = your gaming device. Destination port = 3074:3079 Source port = 1024:65535

"1-65535. Src dst" That's basically saying any port connecting to any port. It's a completely pointless rule.

The first screenshot is wrong because the source and destination ports will never be the same. The first rule in the second screenshot is correct. I have used wireshark and I can confirm that the in game data uses port 3074 on PC. The first 1023 ports are 'reserved', so you should maybe tweak it to 1024-65535, but that shouldn't impact your gaming at all.