From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: [Thread split] nftables rule optimization - dropping invalid in ingress?
Date: Sun, 21 Apr 2024 17:50:00 -0000 [thread overview]
Message-ID: <20240421175000.5fa666d7@localhost> (raw)
In-Reply-To: <rNVqfcHpj4XyJlxISjkKDdyRHbyPqlyF8MOHq07xz1_V3vc99maPQTsAuxgA2PZNbvff2dUfl2s0YdJBI4muw8A7FiMeKu2KvnjK0fG7kYo=@proton.me>
On Sun, 21 Apr 2024 03:45:31 +0000 Eric wrote:
> I'd be very interested in seeing some statistics on how many actual
> invalid packets you see on a live link. Stick some counters in there
> and collect dropped versus passed packets...
This particular system is a desktop one (rebooted often), so that kind
of stats won't make any sense.
> My naive guess would be there are only tiny percentage of rejected
> packets.
Without a particular attack - quite possible. However, it is always
good to learn what is better/worse/futile.
prev parent reply other threads:[~2024-04-21 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 8:48 [Thread split] nftables rule optimization - dropping invalid in ingress? William N.
2024-04-20 18:37 ` William N.
2024-04-20 19:16 ` Kerin Millar
2024-04-21 17:47 ` William N.
2024-04-27 19:23 ` William N.
2024-04-21 3:45 ` Eric
2024-04-21 5:47 ` Slavko
2024-04-21 17:50 ` William N. [this message]
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=20240421175000.5fa666d7@localhost \
--to=netfilter@riseup.net \
--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).