All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: netfilter@vger.kernel.org
Subject: Re: Allowing closed connections time to drain before logging packets
Date: Mon, 30 Sep 2024 11:51:54 +0200	[thread overview]
Message-ID: <Zvp0uij4kC6Vjj9p@calendula> (raw)
In-Reply-To: <97d9d783d0ff4ac494b909176f2a99df2d1190e5.camel@interlinx.bc.ca>

On Wed, Sep 25, 2024 at 01:09:38PM -0400, Brian J. Murrell wrote:
> I often see entries such as this being logged in my system log:
> 
> IN=ens3 OUT= MAC=[redacted] SRC=[redacted] DST=10.75.26.3 LEN=74 TOS=0x00 PREC=0x00 TTL=43 ID=3769 DF PROTO=TCP SPT=33944 DPT=22 WINDOW=229 RES=0x00 ACK PSH URGP=0
> 
> I suspect these are packets that come straggling in after a TCP
> connection has been shut down.  Is there any way to have netfilter give
> recently shut down TCP connections a bit of grace time before logging
> packets that have been sent after they were shut down, just to reduce
> the false-positive noise in my logs?

These are packets logged through 'ct state invalid', right?

> Same goes for UDP in fact:
> 
> IN=eth0.2 OUT= MAC=[redacted] SRC=[reacted, remote IP] DST=[redacted, my local IP] LEN=99 TOS=0x00 PREC=0x00 TTL=59 ID=0 DF PROTO=UDP SPT=443 DPT=37242 LEN=79 MARK=0x3f00
> 
> for, for example, QUIC connections.
> 
> Cheers,
> b.
> 



  parent reply	other threads:[~2024-09-30  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 17:09 Allowing closed connections time to drain before logging packets Brian J. Murrell
2024-09-25 18:18 ` Slavko
2024-10-05 18:28   ` Brian J. Murrell
2024-09-30  9:51 ` Pablo Neira Ayuso [this message]
2024-10-05 18:14   ` Brian J. Murrell

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=Zvp0uij4kC6Vjj9p@calendula \
    --to=pablo@netfilter.org \
    --cc=brian@interlinx.bc.ca \
    --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.