From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id A3DE121FBF1 for ; Mon, 3 Aug 2015 07:55:13 -0700 (PDT) Received: by obdeg2 with SMTP id eg2so100735075obd.0 for ; Mon, 03 Aug 2015 07:55:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=34PdiQjshCgCU8EVJn0R3vTT09eg/1bDpBWl4mTmikg=; b=Z1a4p/2vpCBOZ6Az5Mww6gC5SqRF+1l6s6VVVfvMAqzSsj41zeZtY6c/tZUW3RS1RT xECGlYeQkZ6i4uv9g0G09g5HFi+Cnb9bDY/M1TNewHC6aUTD0/JMPPEoo0dGh5n1nCgv c6h66Ie0Br4xsBwUncWROjhW0UyX3aaEFWFimzZELfjBLSRMCax3Ps5+h4zocjCbpH5A r5dc3dcNFmp+QslndVmD+aR40erfkVGEju81b63zKdydiNDTi7L6H42l+OIgzaEw2S21 kZkUX8jx69895LkPYwe0zFT2ISS0enzwUmzQR6xHQSIxxQIbwBA/zL4j//fqbizqKskx bSKw== MIME-Version: 1.0 X-Received: by 10.60.42.230 with SMTP id r6mr17666870oel.9.1438613712607; Mon, 03 Aug 2015 07:55:12 -0700 (PDT) Received: by 10.202.108.12 with HTTP; Mon, 3 Aug 2015 07:55:12 -0700 (PDT) In-Reply-To: <20150803140054.GA5082@sesse.net> References: <20150803140054.GA5082@sesse.net> Date: Mon, 3 Aug 2015 07:55:12 -0700 Message-ID: From: Dave Taht To: "Steinar H. Gunderson" , Battle of the Mesh Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: bloat Subject: Re: [Bloat] came across an unexpected side-effect of bufferbloat X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2015 14:55:42 -0000 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 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 nee= ded >> 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 cou= rse. > > 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 --=20 Dave T=C3=A4ht 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