From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>,
Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] came across an unexpected side-effect of bufferbloat
Date: Mon, 3 Aug 2015 07:55:12 -0700 [thread overview]
Message-ID: <CAA93jw5CGKbq=4L23T1Rt6EAzOZm+=ezQHdMSTXbxep_PNZwoA@mail.gmail.com> (raw)
In-Reply-To: <20150803140054.GA5082@sesse.net>
This is precisely the sort of failures I (perversely) hope to induce
at battlemesh, using flent to drive the network to saturation.
On Mon, Aug 3, 2015 at 7:00 AM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Mon, Aug 03, 2015 at 11:53:40PM +1000, jb wrote:
>> While researching a little I came across a message on the Amazon support
>> forums that said after 3 hours of uploading to Amazon, their cable modem
>> would crash and reboot. The reason was that the SNMP the cable modem needed
>> to stay healthy was timing out (due to the excessive latency induced by the
>> continuous uploading). The author didn't know it was bufferbloat, of course.
>
> FWIW, you don't need bufferbloat for this to fail. A classic thing with
> switches (typically underbuffered rather than overbuffered!) is that when you
> run the links full, the OSPF packets get dropped and eventually your link
> flaps because the other side thinks you're down.
>
> This is one of the reasons why most L3 switches (well, anything that's
> advanced enough to do OSPF or the likes in the first place :-) ) have QoS at
> all: You need to protect your administrative traffic.
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
prev parent reply other threads:[~2015-08-03 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 13:53 jb
2015-08-03 14:00 ` Steinar H. Gunderson
2015-08-03 14:11 ` Bill Ver Steeg (versteb)
2015-08-03 14:55 ` Dave Taht [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
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='CAA93jw5CGKbq=4L23T1Rt6EAzOZm+=ezQHdMSTXbxep_PNZwoA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=battlemesh@ml.ninux.org \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.com \
/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