Hi Dave,
I have a question regarding FlexQoS and the custom rules that can be added. I think you've previously stated that the most important rule should sit at the bottom of the table to avoid it being overridden by a subsequent rule.
When configuring Cisco routers (e.g. access lists, etc), the most explicit rules are normally placed above the generic rules because the router will stop processing rules as soon as it has a match. For example:
Permit 192.168.1.100 255.255.255.255
Deny 192.168.1.0 255.255.255.0
If those commands were reversed, the 'permit' rule would never get processed.
Does FlexQoS continue to process rules, even if it has already matched a rule? If so, isn't this a waste of CPU resources (every single packet could get processed against 24 rules) and also potentially adds a delay because the packet can't be routed until all 24 rules have been processed?
I have finally managed to perform a wireshark capture* for 'Call of Duty Warzone' and discovered that all 'in game' traffic is bound to Internal UDP port 3074.
Ideally, I'd like to have two gaming rules configured:
- Rule 1
- Internal IP address = Gaming PC
- Internal port = UDP 3074
- Marking = 000000
- Class = Net Control (?) to give it the highest possible priority on the network.
- Rule 2
- Internal IP address = Gaming PC
- Remote port = !80,443
- Marking = 000000
- Class = Gaming
I would have thought that Rule 1 should appear before Rule 2 in any table because it is a more specific match. This would allow it to be processed first and then any other packets, that fail to match Rule 1, can be processed by Rule 2.
Thanks,
* Wireshark is blocked and the game automatically shuts down if it is detected. I renamed the wireshark.exe file and that allowed me to grab the in game data.