Regression #13026
Updated by Marcos M over 2 years ago
h3. SETUP
@/tmp/rules.limiter@ (no change between versions)
<pre>
pipe 1 config bw 5Mb queue 1000 droptail
sched 1 config pipe 1 type fq_codel target 5ms interval 100ms quantum 1514 limit 10240 flows 1024 ecn
queue 1 config pipe 1 droptail
pipe 2 config bw 50Mb queue 1000 droptail
sched 2 config pipe 2 type fq_codel target 5ms interval 100ms quantum 1514 limit 10240 flows 1024 ecn
queue 2 config pipe 2 droptail
</pre>
@grep match /tmp/rules.debug@
<pre>
====================================
22.01
====================================
match out on { vmx1 } inet from 192.0.2.0/28 to any ridentifier 1649027215 dnqueue( 1,2) label "USER_RULE"
====================================
22.05.a.20220403.0600
====================================
match out on { vmx1 } inet from 192.0.2.0/28 to any ridentifier 1649027215 dnqueue( 1,2) label "id:1649027215" label "USER_RULE"
</pre>
h3. TEST
Speedtest from client device behind LAN
h3. RESULTS
Download and Upload limiters do not limit traffic when using floating match rule on pfSense @22.05.a.20220403.0600@; limiters work on @22.01@. rule. Download and Upload results: @Diagnostics / Limiter Info@
See attached limiter_info.txt