netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: DoS/DDoS protection for end nodes
Date: Wed, 17 Apr 2024 19:43:40 -0000	[thread overview]
Message-ID: <20240417194340.20430839@localhost> (raw)

Hi,

I have been searching and reading, and reading... I understand this is
a huge and complex subject, especially for a non-expert. I read earlier
discussions on this ML - some answers seem to say it is futile (i.e.
something that should be done by the ISPs, not by the end clients),
others suggest there is benefit in doing at least what is possible. So,
I hope to have some things clarified by the experts here.

XY: I am trying to do what is right for the network security of a SOHO
LAN. The nodes are distrusted, i.e. there is no assumption that they
are/will always be "clean" just because they are on the LAN.

My questions:

1. Is there a point to attempt DoS/DDoS protection directly on the LAN
nodes (Linux based)?

2. What is the right approach (using nftables)?

             reply	other threads:[~2024-04-17 19:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 19:43 William N. [this message]
2024-04-17 20:25 ` DoS/DDoS protection for end nodes Serg
2024-04-18 12:13   ` William N.
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=20240417194340.20430839@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).