From: Florian Westphal <fw@strlen.de>
To: Martin Zaharinov <micron10@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter <netfilter@vger.kernel.org>,
netfilter-devel@vger.kernel.org, pablo@netfilter.org
Subject: Re: bug report and future request
Date: Tue, 22 Mar 2022 11:32:03 +0100 [thread overview]
Message-ID: <20220322103203.GD24574@breakpoint.cc> (raw)
In-Reply-To: <4B0C8933-C7D8-49BA-B7F2-29625B0865C1@gmail.com>
Martin Zaharinov <micron10@gmail.com> wrote:
> Hi Florian
>
> Look good this config but not work after set user not limit by speed.
Works for me. Before:
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 5.09 GBytes 4.37 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 5.08 GBytes 4.36 Gbits/sec receiver
After:
[ 5] 0.00-10.00 sec 62.9 MBytes 52.7 Mbits/sec 0 sender
[ 5] 0.00-10.00 sec 59.8 MBytes 50.1 Mbits/sec receiver
> table inet nft-qos-static {
> set limit_ul {
> typeof ip saddr
> flags dynamic
> elements = { 10.0.0.1 limit rate over 5 mbytes/second burst 6000 kbytes, 10.0.0.254 limit rate over 12 mbytes/second burst 6000 kbytes }
> }
> set limit_dl {
> typeof ip saddr
> flags dynamic
> elements = { 10.0.0.1 limit rate over 5 mbytes/second burst 6000 kbytes, 10.0.0.254 limit rate over 12 mbytes/second burst 6000 kbytes }
> }
>
> chain upload {
> type filter hook postrouting priority filter; policy accept;
> ip saddr @limit_ul drop
> }
> chain download {
> type filter hook prerouting priority filter; policy accept;
> ip saddr @limit_dl drop
> }
daddr?
> With this config user with ip 10.0.0.1 not limited to 5 mbytes ,
> When back to this config :
>
> table inet nft-qos-static {
> chain upload {
> type filter hook postrouting priority filter; policy accept;
> ip saddr 10.0.0.1 limit rate over 5 mbytes/second burst 6000 kbytes drop
> }
>
> chain download {
> type filter hook prerouting priority filter; policy accept;
> ip daddr 10.0.0.1 limit rate over 5 mbytes/second burst 6000 kbytes drop
~~~~~
next prev parent reply other threads:[~2022-03-22 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 20:44 bug report and future request Martin Zaharinov
2022-03-21 21:27 ` Florian Westphal
2022-03-22 7:14 ` Martin Zaharinov
2022-03-22 10:32 ` Florian Westphal [this message]
2022-03-22 22:55 ` Martin Zaharinov
2022-03-24 7:52 ` Martin Zaharinov
2022-03-24 12:09 ` Martin Zaharinov
2022-03-24 12:20 ` Pablo Neira Ayuso
2022-03-24 12:23 ` Martin Zaharinov
2022-03-24 21:43 ` Martin Zaharinov
2022-04-05 14:12 ` Martin Zaharinov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220322103203.GD24574@breakpoint.cc \
--to=fw@strlen.de \
--cc=micron10@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox