From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Antonio Ojea <antonio.ojea.garcia@gmail.com>,
Florian Westphal <fw@strlen.de>,
netfilter@vger.kernel.org
Subject: Re: Most optimal method to dump UDP conntrack entries
Date: Mon, 11 Nov 2024 13:09:46 +0100 [thread overview]
Message-ID: <20241111120946.GA13430@breakpoint.cc> (raw)
In-Reply-To: <ZzHzTvYFOPcfWvRs@calendula>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > This is how it is implemented today and it works, but it does not
> > handle process restarts per example, or is not resilient to errors.
> > The implementation is also much more complex because we need to
> > implement all the possible edge cases that can leave stale entries
>
> It should also be possible to shrink timeouts on restart via conntrack -U
> which would be similar to the approach that Florian is proposing, but from
> control plane rather than updating existing UDP timeout policy.
The time and effort needed to make something as basic as NAT
work properly is jus silly.
Lets fix conntrack so this "just works".
next prev parent reply other threads:[~2024-11-11 12:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 10:26 Most optimal method to dump UDP conntrack entries Antonio Ojea
2024-10-17 12:46 ` Florian Westphal
2024-10-17 16:36 ` Pablo Neira Ayuso
2024-10-17 22:10 ` Antonio Ojea
2024-10-17 23:30 ` Florian Westphal
2024-10-18 11:05 ` Antonio Ojea
2024-10-18 11:33 ` Florian Westphal
2024-10-18 14:10 ` Antonio Ojea
2024-10-21 13:53 ` Florian Westphal
2024-10-23 9:03 ` Benny Lyne Amorsen
2024-11-10 21:50 ` Florian Westphal
2024-11-11 6:33 ` Antonio Ojea
2024-11-11 12:06 ` Pablo Neira Ayuso
2024-11-11 12:09 ` Florian Westphal [this message]
2024-11-11 12:29 ` Pablo Neira Ayuso
2024-11-11 12:54 ` Florian Westphal
2024-11-12 9:16 ` Pablo Neira Ayuso
2024-11-12 9:20 ` Pablo Neira Ayuso
2024-11-12 14:41 ` Antonio Ojea
2024-11-12 14:43 ` Antonio Ojea
2024-11-12 16:18 ` Florian Westphal
2024-11-15 4:11 ` Antonio Ojea
2024-12-01 17:00 ` Antonio Ojea
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=20241111120946.GA13430@breakpoint.cc \
--to=fw@strlen.de \
--cc=antonio.ojea.garcia@gmail.com \
--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