From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tony He <huangya90@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Fwd: question about using conntrack to change the mark
Date: Mon, 21 Aug 2023 14:02:42 +0200 [thread overview]
Message-ID: <ZONSYn2VHXlbRHX8@calendula> (raw)
In-Reply-To: <CAAUX2SVPgu5Mp8DAhEGzW7Y3UB2k++_qaVeZ3NbHZu4Yfw4bkw@mail.gmail.com>
On Mon, Aug 21, 2023 at 07:26:54PM +0800, Tony He wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> 于2023年8月21日周一 18:29写道:
[...]
> > https://patchwork.ozlabs.org/project/netfilter-devel/patch/20230821101751.4083-1-pablo@netfilter.org/
>
> This patch works when the conntrack sessions are not many. When there are about
> 300 sessions, another error "No buffer space available" is reported.
>
> Works when sessions are not many:
> root@OpenWrt:~# ./conntrack -L -p tcp |wc -l
> conntrack v1.4.7 (conntrack-tools): 204 flow entries have been shown.
> 204
> root@OpenWrt:~# ./conntrack -U -p tcp -m 1
[...]
> tcp 6 96 TIME_WAIT src=192.168.1.30 dst=10.40.9.83 sport=45714
> dport=80 packets=7 bytes=450 src=10.40.9.83 dst=10.40.9.165 sport=80
> dport=45714 packets=6 bytes=11265 [ASSURED] mark=1 use=2
> conntrack v1.4.7 (conntrack-tools): Operation failed: No buffer space available
Another patch to fix this issue, thanks for reporting:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20230821120105.29538-1-pablo@netfilter.org/
next prev parent reply other threads:[~2023-08-21 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAUX2SVTLxtpzsMnKWCpjRZwAKn391rm5T=y=oHPQ_T1w2UpBA@mail.gmail.com>
2023-08-21 7:44 ` Fwd: question about using conntrack to change the mark Tony He
2023-08-21 10:29 ` Pablo Neira Ayuso
2023-08-21 11:26 ` Tony He
2023-08-21 12:02 ` Pablo Neira Ayuso [this message]
2023-08-22 2:11 ` Tony He
2023-08-22 8:51 ` Pablo Neira Ayuso
2023-08-22 9:46 ` Tony He
2023-08-22 10:00 ` Pablo Neira Ayuso
2023-08-22 10:09 ` Tony He
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=ZONSYn2VHXlbRHX8@calendula \
--to=pablo@netfilter.org \
--cc=huangya90@gmail.com \
--cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.