From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: DoS/DDoS protection for end nodes
Date: Thu, 18 Apr 2024 12:13:40 -0000 [thread overview]
Message-ID: <20240418121340.58c1fa6e@localhost> (raw)
In-Reply-To: <7370616d-fa0a35c7-09c3-4db9-9b8c-03b944b73124-at.encryp.ch-74726170@at.encryp.ch>
On Wed, 17 Apr 2024 20:25:51 +0000 Serg wrote:
> Your question is too broad,
Yes, because the subject itself is broad and I am trying to figure the
general idea correctly. AFAIU, it is performance.
> However, for high-performance scenarios, XDP is a better alternative
> to nftables.
After reading your reply, I did more reading. A few interesting links
(out of many which I read) from this additional research:
https://cilium.io/blog/2018/04/17/why-is-the-kernel-community-replacing-iptables/
https://github.com/mbertrone/bpf-iptables
https://www.phoronix.com/news/BPFILTER-2021
IIUC, there is this general long-term idea to move from
iptables/nftables rules to BPF (bpfilter), thus gaining performance and
there have been PoCs about that back in 2018. I could not find info
about how this has actually progressed (as it would really not be fun
to write firewall rules in C, parallel to using nftables).
What can you tell me about that?
How suitable is Cilium for SOHO needs?
Is bpfilter practical or not yet? Any documentation about it?
Am I looking at the wrong things?
next prev parent reply other threads:[~2024-04-18 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 19:43 DoS/DDoS protection for end nodes William N.
2024-04-17 20:25 ` Serg
2024-04-18 12:13 ` William N. [this message]
2024-04-18 14:11 ` Florian Kauer
2024-04-18 15:32 ` William N.
2024-04-18 16:16 ` Serhii
2024-04-18 16:31 ` William N.
2024-04-20 20:10 ` Kerin Millar
2024-04-21 9:10 ` William N.
2024-04-22 14:42 ` Quentin Deslandes
2024-04-22 15:12 ` William N.
2024-04-22 15:27 ` Quentin Deslandes
2024-04-22 17:32 ` William N.
2024-04-17 20:47 ` Reindl Harald
2024-04-17 21:24 ` Joshua Moore
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=20240418121340.58c1fa6e@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).