Re: problem with limit rate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you for suggestion.
When i set burst value of 1 it will trigger after 1 burst packet or after 31 normal/not burst packets.

So it is not possible to just: set nftables to do something over 30 packets per minute regardless normal packets or bust ?

On 05.01.2019 19:28, Florian Westphal wrote:
GM <grzesiek20@xxxxxx> wrote:
When i include burst in my ruleset it works as expected with burst. I
simulate this with nmap --bad-sum but when there is no burst e.g delay
between packets is 1s
nmap --bad-sum --scan-delay 1s
behavior is very strange because it drops 60 packets instead of 30. How to
explain this ?
It first consumes the burst, then the rate.

nft limit works like -m limit in iptables.

If you want the '1s delay' case to match on 30 packets, try a burst
value of 1.


--
Pozdrawiam
Grzesiek M.




[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux