07-16-2022 09:58 AM
Hello.
I have posted on forums in the past about the use of ARC and DSCP tagging.
ARC dscp and WMM(TOS) dscp Inconsistency. - Commscope (ruckuswireless.com)
I found out today on my R650 that the DSCP tags I set in the windows 10 client are not being properly classified in the AP.
First of all, there is no problem with the R610, it only happens with the R650. Both APs use the latest version of firmware. 200.12.10.105.129.
I set IDM (internet download manager) to AF11 on Windows 10 client.
< New-NetQosPolicy -Name "idm" -AppPathNameMatchCondition "IDMan.exe" -DSCPAction 10 >
I also set the TOS value of the background on the R650.
< tos classification background 0x28 >
However, some downloads through idm (e.g. Google Drive) are being classified and processed as besteffort rather than background in AP. The problem is that some are classified as background and some as besteffort. So it's hard to pinpoint the problem.
When I capture packets via tcpdump or wireshark on router and my laptop, they all show up as AF11.
If I turn ARC off, there is no problem, all of them are correctly classified as background.
I'm explaining now, but I don't know if you guys will be able to reproduce and solve the problem.
In summary, the problem is that some packets are misclassified in WMM QoS when ARC function is turned on in R650.
ruckus(debug)# remote_ap_cli -A "get mqstats wlan32 all"
---- Command 'rkscli -c "get mqstats wlan32 all "' executed at 8c:7a:15:xx:xx:xx
STA: 6a:fc:34:xx:xx:xx AID:16
----------------------------------------------------------------------------------------------------
Qued ovrflw enq deq Airtime reenq deact XRetries XTlimits Flags
mgmt ( 0) X: 0 0 0 0 0 0 0 0
data VO( 3) A 33 0 30 30 0 33 0 0 0 14000C
data VI( 2) A 0 0 0 0 0 0 0 0 0 0
data BE( 1) A 11814 0 10538184 10538184 0 4074984 0 0 0 10010D
data BK( 0) A 47207 0 861179 861179 0 309347 0 0 0 14000C
========================================TID FLAGS===================================================
SCHQ PAUS AMPDU AMSDU DEL RAW MCST REQ HWQ SWQ_HWQ NOT_Q NOT_RX TF_TE TID_AIR
0 0 1 1 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 0 1 1 0 0 0 0 1 0 0 0 0 0
0 0 1 1 0 0 0 0 0 0 0 0 0 0
OK
---- Command Execution Summary:
success: 1
failure: 0
total: 1
remote_ap_cli -A get mqstats wlan32 all
10-30-2022 01:56 AM - edited 11-01-2022 06:55 AM
The problem appears to be due to an iptables rule manipulating packets on my router.
After deleting certain rule, there is no problem.
Anyway, R610 and R650 behaved a little differently and R610 did a good job of classifying packets as background even with packet modifications via iptables rules.
With the R650 running ARC, connection tracking seems to work a bit differently.
If there is a change in the first packets, even if subsequent packets come with DSCP tags, wmm-qos does not properly classify them.