From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: ju@klipix.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] fq_codel through Tor
Date: Sat, 19 Jan 2013 11:03:01 +0100 [thread overview]
Message-ID: <CAMZR1YC7y1CVTr6GkR2p+6R5tocm9AR_hGxXdGjUWYQn0E1=xw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6uTnht1sB9VhB-UXuBgrJSQ97yj0wdNGQU7JmtwrL__g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
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" <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äht
>
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 2037 bytes --]
next prev parent reply other threads:[~2013-01-19 10:03 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 [this message]
2013-01-19 13:39 ` dpreed
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='CAMZR1YC7y1CVTr6GkR2p+6R5tocm9AR_hGxXdGjUWYQn0E1=xw@mail.gmail.com' \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=ju@klipix.org \
/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