From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from darwin.kenyonralph.com (darwin.kenyonralph.com [173.255.215.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 31A9621F1E1 for ; Mon, 26 Aug 2013 12:01:56 -0700 (PDT) Received: from darwin.kenyonralph.com (localhost [IPv6:::1]) by darwin.kenyonralph.com (Postfix) with ESMTP id CFB7EE0B5 for ; Mon, 26 Aug 2013 12:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=kenyonralph.com; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=postfix; bh=q0v3bLPvc1VOdk1s2Uwyq7fajwo=; b=b7To MaZx+Hh5ThI922H4niE0+jgMoTsB66h1eEXDR0TpR7UzzAyyvOBHXHofUN9v5c56 aOu50xyPKokPcBIW5xkzKNnvWz+3VQabjt/PvmcSbatRyfbaJLMApF3Ju3uREEIr iku1XNc+2b6vPjnw3G+wiX82TEKHfmbemQvD0fs= DomainKey-Signature: a=rsa-sha1; c=simple; d=kenyonralph.com; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=postfix; b=JAw0ozY0ZEOuAKMR2x7aCcfNgjPhFc Y2aMYs81iLuOKe3ad4pvDb+6v0J1xIdfNIwMrng0u4x/y83HJ9aQ0Xsf1iBXTD70 g+UrxPHK2p7imB7ST8EZzM+kdcaEyn4fLpHPgZX1C3zraeo0j7IOhRfdffaixCAM kA792IrHsWlws= Received: by darwin.kenyonralph.com (Postfix, from userid 1000) id B438FE0B1; Mon, 26 Aug 2013 12:01:55 -0700 (PDT) Date: Mon, 26 Aug 2013 12:01:55 -0700 From: Kenyon Ralph To: bloat@lists.bufferbloat.net Message-ID: <20130826190155.GI23831@kenyonralph.com> Mail-Followup-To: bloat@lists.bufferbloat.net References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QxN5xOWGsmh5a4wb" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Bloat] how to fix modem buffer bloat? 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, 26 Aug 2013 19:01:56 -0000 --QxN5xOWGsmh5a4wb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2013-08-26T14:53:44-0400, Collin Anderson wrote: > Hi All, >=20 > > Any recommendations for solving the bufferbloat on my Comcast SMC cable= modem? >=20 > Looking at it more, a workaround is probably all I can hope for at > this point. I first started keeping a ping session open back in 2008 > to debug the internet, and I see bufferbloat almost every day at home > and at work. Anything to avoid the symptoms sounds great. >=20 > I want something reliable and have minimal configuration. I'm thinking > about buying a WNDR3800 and installing CeroWRT, or is there better > recommended hardware? >=20 > Also, isn't fq_codel "on by default" [1] in OpenWRT? If so, what's the > advantage of CeroWRT? WNDR3800 with OpenWrt and properly configured and activated /etc/config/qos which uses fq_codel has been working great for my house. Solves the bufferbloat problem to my satisfaction on my Cox cable connection. > Thanks, > Collin >=20 > [1] http://www.ietf.org/proceedings/87/slides/slides-87-aqm-6.pdf --=20 Kenyon Ralph --QxN5xOWGsmh5a4wb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJSG6YjAAoJEJj/PvnJuRLVg1QP/Rkqna8BL6dRIDOqROClYPDj nQisoagjDFX0sVDeKSqO5erc3Lo2G0NNQMa1XtZsN/yVf1F1osc99zQDDhJ/U1V4 6/CSz0Nwjtb50hJEKLECyM8yHdNiHa3NW1Tt+ALte26R5h7RD/Brhhzl1LPKVSvL TI1FnotHRtbvwXxFHiT+CgXG4l4VxftzoswTSXG4j6gIhjelNZTIJHhwPIiblyNM jpSoN33PHGgPm0lmsIkzloBF7r5rzit/Em0Wdy0go+U7iveEjY7BjOu1u8Gm87PW D5ipXNv+wymqUGhN35TwtL/KdO/Keo68Uu9zzK/sTKE78G5hluAopk3pNTj7bNcK Fv3LSx7cwHMJgUqNk2p7a4IpwHOqnivwoaFuL4+utP520wa2LCgpNNOf77CR0w/Q lLlHTvvQxH0l6TZnvouFDTIZxGwbXs022vyP9YV16TzgRhEZ2yRHEGhA76FSUXmg OIq/hLBZO1alBCOl3NYXZz+q8i/fTqledBF7d1t9ISTQiz3G8RVuZRpYm5nhh9tZ B92CCz3tcWtgcrkiW0ZyhZ8AOsPwXl2w9hSmo1mxBSP+IhS9wkfLYtd68ParYx8T cG0SwwJZph6GevZbDasSIIS+xX1tTP/oO/F2LdzQsjbfiydYh2dZ1N9HWBeQ8Rl/ UenOohC3IYR9h/ildN9Q =hDY3 -----END PGP SIGNATURE----- --QxN5xOWGsmh5a4wb--