From: Florian Westphal <fw@strlen.de>
To: Vitaly Zuevsky <vzuevsky@ns1.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: ctnetlink: remove expired entries first
Date: Fri, 17 Dec 2021 20:04:17 +0100 [thread overview]
Message-ID: <20211217190417.GC17681@breakpoint.cc> (raw)
In-Reply-To: <CA+PiBLze0Qu-AdAeu_0K++HcHaaN+7p383drNyx3y0RdO2FCuA@mail.gmail.com>
Vitaly Zuevsky <vzuevsky@ns1.com> wrote:
> Hi Florian
>
> Do you have any news on this?
> Meanwhile I cloned the repo git://git.netfilter.org/conntrack-tools,
> ran ./autogen.sh to produce configure, and the latter failed with:
>
> checking for rpc/rpc_msg.h... yes
> ./configure: line 13329: syntax error near unexpected token `LIBTIRPC,'
> ./configure: line 13329: ` PKG_CHECK_MODULES(LIBTIRPC, libtirpc >= 0.1)'
>
> Interestingly, PKG_CHECK_MODULES was never defined there. Is that
> repository for production code - I am confused?
Sure. But the patch is for the kernel.
I already mentioned that this doesn't handle anything for non-nat case.
> > > Maybe 'conntrack -L unconfirmed' or 'conntrack -L dying' show something?
Still stands.
Also, is there really a discrepancy? Please show output of
conntrack -C
conntrack -L | wc -l
conntrack -C
"conntrack -L" reclaims dead/timed-out entries, conntrack -C currently
does not.
next prev parent reply other threads:[~2021-12-17 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 16:39 [PATCH nf] netfilter: ctnetlink: remove expired entries first Florian Westphal
2021-12-09 17:08 ` Vitaly Zuevsky
2021-12-09 17:11 ` Florian Westphal
2021-12-09 18:23 ` Vitaly Zuevsky
2021-12-17 18:47 ` Vitaly Zuevsky
2021-12-17 19:04 ` Florian Westphal [this message]
2021-12-17 19:49 ` Vitaly Zuevsky
2021-12-23 17:42 ` Vitaly Zuevsky
2021-12-16 13:10 ` Pablo Neira Ayuso
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=20211217190417.GC17681@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=vzuevsky@ns1.com \
/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.