From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dave.taht@gmail.com>
Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com
	[209.85.223.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client CN "smtp.gmail.com",
	Issuer "Google Internet Authority" (verified OK))
	by huchra.bufferbloat.net (Postfix) with ESMTPS id 66FF121F1FA
	for <cerowrt-devel@lists.bufferbloat.net>;
	Fri, 18 Jan 2013 23:18:10 -0800 (PST)
Received: by mail-ie0-f179.google.com with SMTP id k14so7385738iea.10
	for <cerowrt-devel@lists.bufferbloat.net>;
	Fri, 18 Jan 2013 23:18:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:x-received:date:message-id:subject:from:to
	:content-type; bh=2eX8V7TZVCBRVs+wF3pf3GCQWPi/beWEbXu/YoyVuT8=;
	b=aCvi5InuBsyP/zBUR4304/sWtgG7w8X4Dc1JmpzArIaTj5iN9W1fYF2l7VfC+GyGC+
	/qM7AXZRy3I6C3dh95iZw1deQCIfG/5aiw4k+gSFaB/A0XT9Hmw/Q/hC8t4BRmbrgdG3
	45Q/obHRl5liNQaj3pkeP5ckInGO5DHl2OPXdTZlwmXVsw1Twv4XCx2lHaZhNqx3+/Cm
	XnlFJHFtFtx3EVqBRQpd08ryCt/9p1fC2gT21H9EQEI9Ut+ok9t3AQMqq2hiAKmzx4Lh
	wHyAPlKX7AO/mpG44cxVUSu4ABctudGLwGRQ5Z27KopbzeX0BPuijsRscu3/RI+vV339
	UQhA==
MIME-Version: 1.0
X-Received: by 10.50.88.136 with SMTP id bg8mr4156119igb.96.1358579889698;
	Fri, 18 Jan 2013 23:18:09 -0800 (PST)
Received: by 10.64.135.39 with HTTP; Fri, 18 Jan 2013 23:18:09 -0800 (PST)
Date: Sat, 19 Jan 2013 02:18:09 -0500
Message-ID: <CAA93jw6uTnht1sB9VhB-UXuBgrJSQ97yj0wdNGQU7JmtwrL__g@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net, ju@klipix.org
Content-Type: multipart/alternative; boundary=e89a8f235a17b975e504d39f0777
Subject: [Cerowrt-devel] fq_codel through Tor
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
	<cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
	<mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 07:18:10 -0000

--e89a8f235a17b975e504d39f0777
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

https://srv1.openwireless.org/pipermail/tech/2012-December/000332.html

I haven't the foggiest idea what this traffic would look like. Is it even
possible to induce bufferbloat through tor?

--=20
Dave T=E4ht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

--e89a8f235a17b975e504d39f0777
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<a href=3D"https://srv1.openwireless.org/pipermail/tech/2012-December/00033=
2.html">https://srv1.openwireless.org/pipermail/tech/2012-December/000332.h=
tml</a><br clear=3D"all"><div><br></div><div>I haven&#39;t the foggiest ide=
a what this traffic would look like. Is it even possible to induce bufferbl=
oat through tor?</div>
<div><br></div>-- <br>Dave T=E4ht<br><br>Fixing bufferbloat with cerowrt: <=
a href=3D"http://www.teklibre.com/cerowrt/subscribe.html" target=3D"_blank"=
>http://www.teklibre.com/cerowrt/subscribe.html</a>=20

--e89a8f235a17b975e504d39f0777--