5.0rc3 - 'limit' matcher is broken on x86?

RouterOS General
1

when I add “limit” matcher in Firewall Filter rule, it doesn’t catch packets at all - is it known problem?

RB450G works fine. a feature of multicore system with RPS enabled?..

2

hmmm…

when I add a rule with “connection-state=invalid action=passthrough”, it counts about 7-8 packets per second… when I add “limit=1,5” - it does not catch packets %)

UPD: if I leave “limit” and remove “connection-state” - it counts exactly 1 pps… maybe it’s because there are 5kpps of traffic…

I’d like to use “limit” with “action=log” not to overload the Log…

3

hmm, i just tired to use limit to reduce amount of ping per second - it worked fine on X86 and RB433.

Can you provide exact rules you used?

4

sorry for the long delay - I installed rc4, still have the same problem:

/ip firewall filter add chain=forward connection-state=invalid action=passthrough

shows about 5-20 packets per second. if I change that rule to

/ip firewall filter add chain=forward connection-state=invalid limit=1,5 action=passthrough

then I have zero traffic, ‘packets’ field freezes:
Clipboard01.gif

[admin@Alpha] > sys reso pr
                  version: "5.0rc4"
                      cpu: "Intel(R)"
                cpu-count: 8
            cpu-frequency: 2666MHz
                 cpu-load: 17%
        architecture-name: "x86"
               board-name: "x86"
                 platform: "MikroTik"
[admin@Alpha] >