General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Cc: John Heidemann <johnh@isi.edu>
Subject: [Bloat] industrial scale bufferbloat in a DDOS on core DNS servers
Date: Mon, 6 Jun 2016 11:52:03 -0700	[thread overview]
Message-ID: <CAA93jw49B2-d_onM2toXw14kV5PjGn+jWmLHOLk3-sqGkcttEA@mail.gmail.com> (raw)

I had a lot of papers to read on my vacation. This one, in section 3.3:

"Figure 7 shows the median RTT for selected K-Root sites. Although the
K-AMS site remained up and showed minimal loss, its median RTT showed
a huge increase: from roughly 30 ms to 1 s on Nov. 30, and to almost 2
s on Dec. 1, strongly suggesting the site was overloaded. K-NRT shows
similar behavior, with median RTT rising from 80 ms to 1 s and 1.7 s
in the two events. Overload does not always result in large latencies.
B-Root (a single site) showed only modest RTT increases (Figure 4),
since only few probes could reach it during the attack (Figure 3). We
hypothesize that large RTT increases are the result of an overloaded
link combined with large buffering at routers (industrial-scale
bufferbloat [23])."

from: http://www.isi.edu/~johnh/PAPERS/Moura16a.pdf

The authors did not have any insight into where on the path the RTT
increases were coming from. Now that we have adequate fq and aqm
solutions out there for bsd and linux, perhaps some load balancers
(often bsd based?) are sources of bufferbloat? Or perhaps others in
the dns world, fighting off DDOS attacks, can look harder at where the
RTT increases are from?


-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

                 reply	other threads:[~2016-06-06 18:52 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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw49B2-d_onM2toXw14kV5PjGn+jWmLHOLk3-sqGkcttEA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=johnh@isi.edu \
    /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