From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] pulsed wave ddos attacks
Date: Wed, 2 Nov 2022 10:54:16 -0700 [thread overview]
Message-ID: <CAA93jw6onKenyTQiDwtSWJCcjW4WzcBbX25pZMSGU3oj=XqN7Q@mail.gmail.com> (raw)
Unless done "well", for some sad value of "well", FQ technologies are
very resistant to these sort of attacks, but AQM and FIFOs are not.
fq_codel is actually more resistant in some ways than cake is, because
the direct map hash has collisions.... a well formed against FQ attack
has not been demonstrated, as yet, so far as I know.
https://blog.apnic.net/2022/10/26/acc-turbo-mitigates-pulse-wave-ddos-attacks-using-programmable-switches/
Detection before it hits the customer is hard.
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-11-02 17:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6onKenyTQiDwtSWJCcjW4WzcBbX25pZMSGU3oj=XqN7Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/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