From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Microsoft Secure Server Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id E12A321F0FB; Sun, 9 Dec 2012 08:57:11 -0800 (PST) Received: from mail203-va3-R.bigfish.com (10.7.14.236) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Sun, 9 Dec 2012 16:57:10 +0000 Received: from mail203-va3 (localhost [127.0.0.1]) by mail203-va3-R.bigfish.com (Postfix) with ESMTP id 59B477C01C2; Sun, 9 Dec 2012 16:57:10 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.244.213; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -10 X-BigFish: VPS-10(zz98dI9371I103dK1102I1432Izz1de0h1202h1e76h1d1ah1d2ahzz8275ch17326ah8275bh5eeeKz31h2a8h668h839h946hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h35h1155h) Received-SPF: softfail (mail203-va3: transitioning domain of dartware.com does not designate 157.56.244.213 as permitted sender) client-ip=157.56.244.213; envelope-from=richard.e.brown@dartware.com; helo=CH1PRD0510HT005.namprd05.prod.outlook.com ; .outlook Received: from mail203-va3 (localhost.localdomain [127.0.0.1]) by mail203-va3 (MessageSwitch) id 1355072227834130_27764; Sun, 9 Dec 2012 16:57:07 +0000 (UTC) Received: from VA3EHSMHS016.bigfish.com (unknown [10.7.14.237]) by mail203-va3.bigfish.com (Postfix) with ESMTP id C6CD7620073; Sun, 9 Dec 2012 16:57:07 +0000 (UTC) Received: from CH1PRD0510HT005.namprd05.prod.outlook.com (157.56.244.213) by VA3EHSMHS016.bigfish.com (10.7.99.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 9 Dec 2012 16:57:07 +0000 Received: from CH1PRD0510MB381.namprd05.prod.outlook.com ([169.254.11.104]) by CH1PRD0510HT005.namprd05.prod.outlook.com ([10.255.150.40]) with mapi id 14.16.0245.002; Sun, 9 Dec 2012 16:56:59 +0000 From: Richard Brown To: Richard Brown Thread-Topic: Bufferbloat at LUG talk - Meeting Report Thread-Index: AQHN1i4zQ54TxhwNYkGaVJpoiVv9nw== Date: Sun, 9 Dec 2012 16:56:58 +0000 Message-ID: <54532012A5393D4E8F57704A4D55237E3CE5C5E7@CH1PRD0510MB381.namprd05.prod.outlook.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.150.4] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: dartware.com Cc: "cerowrt-devel@lists.bufferbloat.net" , bloat Subject: Re: [Bloat] Bufferbloat at LUG talk - Meeting Report 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: Sun, 09 Dec 2012 16:57:12 -0000 Folks, I gave the talk to the local Linux User Group on Thursday, and it went real= ly well. Two people came up to me after the talk and said, in effect, "You = know, I think I've seen this. But I've always blamed something else." Their= experience: - Attempting to Skype with a bunch of web browser tabs open gives bad resul= ts. Closing the tabs made things better. (They been blaming the browser for= "using too much memory". Now it's possible to think that it's a network pr= oblem.) - Another person reported that his network connection (wireless ISP, two ho= ps to a wired network) seemed to work OK as long as his household was mostl= y downloading. But uploading much of anything really made things bad. I posted the slides at http://www.bufferbloat.net/attachments/download/148/= Bufferbloat-DLSLUG-Dec2012.pdf Rich PS I've updated the CeroWrt site to include links to a bunch of relevant vi= deos. (http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos) Pleas= e let me know if there are others that we should point to. On Nov 25, 2012, at 8:11 PM, Richard E. Brown wrot= e: > Folks, >=20 > I am planning to give a talk about Bufferbloat to the local Linux User Gr= oup next week (http://dlslug.org). All this traffic on the list is fantasti= c, because it gives me a lot of background on the current state of bufferbl= oat. I've pulled together a bunch of general questions about CeroWrt that I= would like to be able to cover if they come up: >=20 > - Is it true that the latest CeroWrt is Sugarland 3.3.8-26 from mid-Septe= mber? (My router is using this build - r33460.)=20 >=20 > - I see the "QoS" item in the Network tab of the web GUI. Is this importa= nt for Sugarland? Or does some other router configuration take care of this= now? >=20 > - What's the relationship between the QoS GUI item above and the debloat.= sh and simple_qos.sh scripts that have been mentioned on this list? What's = the best practice here for getting a router up and running? >=20 > - I can see how the CeroWrt de-bloating algorithms help protect against b= ad latency when I'm *uploading* big files. I'm not sure whether using CeroW= rt with its CoDel/FQ/SFQ/etc. helps when I'm downloading big files, though.= What can I say about this? >=20 > - I believe the default DNS server in Sugarland is dnsmasq, not bind. Is = DNSSEC enabled by default? Also: there's a report (Bug #411) that says that= DNS is leaking internal names to the outside world. What's the best advice= for closing this? ("list notinterface 'ge00'" is one recommendation=85) >=20 > - I've been assembling information about the various de-bloating techniqu= es implemented in CeroWrt. It seems that Infoblox has recently reorganized = their blogs, and the links published earlier this week have all broken. Her= e are updates: >=20 > http://www.infoblox.com/community/blog/application-analysis-using-tcp-ret= ransmissions-part-1 > http://www.infoblox.com/community/blog/application-analysis-using-tcp-ret= ransmissions-part-2 > http://www.infoblox.com/community/blog/router-buffer-tuning > http://www.infoblox.com/community/blog/rethinking-interface-error-reports >=20 > My plan is to give a little of the science behind bufferbloat mitigation = and also put in a plug for CeroWrt. Any topics I haven't already mentioned = that I should? Thanks! >=20 > Rich Brown > Hanover, NH USA