From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175]) (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 7402B21F208 for ; Sat, 19 Jan 2013 02:03:02 -0800 (PST) Received: by mail-ob0-f175.google.com with SMTP id vb8so4578479obc.34 for ; Sat, 19 Jan 2013 02:03:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=bbycEI5Pvdyq+XDEgBry9uau5XoXrnYYGH3IhvAIk0Y=; b=iy0rayuA6t4LQTR2DMS5IJh8iHmRRKy7dGVgTVW1+G7N264xsM7Xx1qgzcJIlWwA5y Iz8NcqQ7nxFpCVriGwj6eXXL/A4yKeCoWVWjFAoE6jxBk0XdSJTmeg80EXSgiXD30pCz NOCKMgSQoroLDjPnRzLPBh+vglZj+Dk/T8G+xD6QppRX2Irwld653ns6JFIL+O5CnYM+ iJnM/VxwIk6ZgNP4XlpFo7XJHMtyweRaMz2xlmlbw+zFbuY83NHlHJUYsOfu44b2Mwyf 6YmeL8eL8Y4OBJjSRZ8/0qksBz+6at68lQstgX+LaZ/Ar2r3mwil/4K8wbgIZ74eWa6w gZ5w== MIME-Version: 1.0 X-Received: by 10.60.27.69 with SMTP id r5mr3191159oeg.102.1358589781568; Sat, 19 Jan 2013 02:03:01 -0800 (PST) Received: by 10.76.82.73 with HTTP; Sat, 19 Jan 2013 02:03:01 -0800 (PST) X-Originating-IP: [77.65.47.165] Received: by 10.76.82.73 with HTTP; Sat, 19 Jan 2013 02:03:01 -0800 (PST) In-Reply-To: References: Date: Sat, 19 Jan 2013 11:03:01 +0100 Message-ID: From: Maciej Soltysiak To: Dave Taht Content-Type: multipart/alternative; boundary=e89a8f838c13536d3a04d3a15564 X-Gm-Message-State: ALoCoQntFztRWzePVezuyARMwDdMJYrdl7z+Iy4AsRNHMXwLQZlMVoF3krbpblhBllkwgO+Yd4F4 Cc: ju@klipix.org, cerowrt-devel@lists.bufferbloat.net Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2013 10:03:02 -0000 --e89a8f838c13536d3a04d3a15564 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Funny you should ask. Being inspired by Tor's Jacob Applebaum's keynote at #29C3 ( http://isoc-ny.org/p2/4650 ) I started a tor node. Without throttling the effect on my box was similar to bittorrent : instantly dozens of connections consuming in total 4-5 MB/s inwards and outwards. Observed in iptraf. ssh felt a bit laggy. I think much depends on your exit a policy. If you allow all no port restrictions (default) you might be serving a lot, perhaps even bit torrent= ; I saw a headline somewhere about ways to circumvent tor policy to run torrents. SO unbloated devices may be keen on unbloating to still live with being generous to tor which is very important for the project as the main issue with it is it's slowness. Maciej On 19 Jan 2013 09:57, "Dave Taht" wrote: > 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? > > -- > Dave T=C3=A4ht > > Fixing bufferbloat with cerowrt: > http://www.teklibre.com/cerowrt/subscribe.html > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > > --e89a8f838c13536d3a04d3a15564 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Funny you should ask. Being inspired by Tor's Jacob Appl= ebaum's keynote at #29C3 ( http:= //isoc-ny.org/p2/4650 ) I started a tor node. Without throttling the ef= fect on my box was similar to bittorrent : instantly dozens of connections = consuming in total 4-5 MB/s inwards and outwards. Observed in iptraf. ssh f= elt a bit laggy.

I think much depends on your exit a policy. If you allow all= no port restrictions (default) you might be serving a lot, perhaps even bi= t torrent;

I saw a headline somewhere about ways to circumvent tor poli= cy to run torrents.

SO unbloated devices may be keen on unbloating to still live= with being generous to tor which is very important for the project as the = main issue with it is it's slowness.

Maciej

On 19 Jan 2013 09:57, "Dave Taht" <= dave.taht@gmail.com> wrote:
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?

--
Dave T=C3=A4ht

Fixing bufferbloat with cerowrt= : http://www.teklibre.com/cerowrt/subscribe.html=20
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel

--e89a8f838c13536d3a04d3a15564--