[Cerowrt-devel] fq_codel through Tor

[dpreed at reed.com]

Tor should be following the same rules as routers - buffer minimally, signal congestion quickly (by packet drop, ECN, etc. on an end-to-end basis).  I bet it does *not* do the latter at its layer, and I bet the underlying (non Tor) layer does not.
 
Remember - using fq_codel in a "home router" does not fix the real problem in the DOCSIS deployment, nor does it fix the real problem in the LTE deployment.  By fixing the "outgoing rate" less than the "service rate", you just never use (hopefully) the buffers in your cable modem uplink, which are not shared with other users.
 
But Tor is a system of "routers" (onion-y ones), and its own "software" needs to be fixed.
 
Is anyone actually fixing the Tor router layer?
 
That's not sufficient, because the layer 2 below the IP layer *under* Tor will still be bad.
 
But it may not be worth fixing one layer without fixing the other.
 
Tor's buffering should be studied.
 
-----Original Message-----
From: "Maciej Soltysiak" <maciej at soltysiak.com>
Sent: Saturday, January 19, 2013 5:03am
To: "Dave Taht" <dave.taht at gmail.com>
Cc: ju at klipix.org, cerowrt-devel at lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] fq_codel through Tor



Funny you should ask. Being inspired by Tor's Jacob Applebaum's keynote at #29C3 ( [http://isoc-ny.org/p2/4650] 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" <[mailto:dave.taht at gmail.com] dave.taht at gmail.com> wrote:
[https://srv1.openwireless.org/pipermail/tech/2012-December/000332.html] 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äht

Fixing bufferbloat with cerowrt: [http://www.teklibre.com/cerowrt/subscribe.html] http://www.teklibre.com/cerowrt/subscribe.html 
_______________________________________________
 Cerowrt-devel mailing list
[mailto:Cerowrt-devel at lists.bufferbloat.net] Cerowrt-devel at lists.bufferbloat.net
[https://lists.bufferbloat.net/listinfo/cerowrt-devel] https://lists.bufferbloat.net/listinfo/cerowrt-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/cerowrt-devel/attachments/20130119/767f2997/attachment-0002.html>