From: dpreed@reed.com
To: "Maciej Soltysiak" <maciej@soltysiak.com>
Cc: ju@klipix.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] fq_codel through Tor
Date: Sat, 19 Jan 2013 08:39:06 -0500 (EST) [thread overview]
Message-ID: <1358602746.910329141@apps.rackspace.com> (raw)
In-Reply-To: <CAMZR1YC7y1CVTr6GkR2p+6R5tocm9AR_hGxXdGjUWYQn0E1=xw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2753 bytes --]
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@soltysiak.com>
Sent: Saturday, January 19, 2013 5:03am
To: "Dave Taht" <dave.taht@gmail.com>
Cc: ju@klipix.org, cerowrt-devel@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@gmail.com] dave.taht@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@lists.bufferbloat.net] Cerowrt-devel@lists.bufferbloat.net
[https://lists.bufferbloat.net/listinfo/cerowrt-devel] https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 4009 bytes --]
next prev parent reply other threads:[~2013-01-19 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 7:18 Dave Taht
2013-01-19 9:17 ` David Lang
2013-01-19 10:03 ` Maciej Soltysiak
2013-01-19 13:39 ` dpreed [this message]
2013-01-19 16:42 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1358602746.910329141@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ju@klipix.org \
--cc=maciej@soltysiak.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox