netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <imnozi@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nf-ct-list and nf-exp-delete
Date: Tue, 7 Oct 2025 18:45:31 -0400	[thread overview]
Message-ID: <20251007184531.73f3404d@playground> (raw)
In-Reply-To: <aOT1NhYSS65KwwJD@calendula>

On Tue, 7 Oct 2025 13:10:46 +0200
Pablo Neira Ayuso <pablo@netfilter.org> wrote:

> On Tue, Oct 07, 2025 at 05:15:08AM -0400, imnozi@gmail.com wrote:
> > [iptables v1.8.7; old, but it's what I have.]
> > 
> > Why does 'nf-exp-delete -i [id]' *not* remove remove some conntrack entries even after being told to remove them multiple times? It deletes most entries for my purposes (if condition is met, delete conntrack entry and block the IP using ipset). Blocked IPs are DROPped on internet side, and RESET and REJECTed on the internal side. But from time to time, I see ESTABLISHED conns that don't get (can't be) deleted.
> 
> nf-exp-delete -i [id] ????

Given:
----
# nf-ct-list --tcp-state=ESTABLISHED --reply-src=10.X.X.2 -f details
tcp ESTABLISHED 188.132.249.148:57992 -> 204.111.X.X:443 10.X.X.2:443 <- 188.132.249.148:57992 mark 17488 
    id 0xf016f3da family inet refcnt 1 timeout 10m 17s <ASSURED,DNAT>
----

then:
----
nf-exp-delete -i 0xf016f3da
----
usually removes that entry from conntrack. In my experience, some entries are not, and cannot be, removed without drastic measures that would interrupt firewall operations.

N

  reply	other threads:[~2025-10-07 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  9:15 nf-ct-list and nf-exp-delete imnozi
2025-10-07 11:10 ` Pablo Neira Ayuso
2025-10-07 22:45   ` imnozi [this message]
2025-10-08 11:50     ` Pablo Neira Ayuso
2025-10-08 21:01       ` imnozi

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=20251007184531.73f3404d@playground \
    --to=imnozi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).