From: Benjamin Cronce <bcronce@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tackling torrent on a 10mbit uplink (100mbit down)
Date: Sun, 21 Jun 2015 11:24:29 -0500 [thread overview]
Message-ID: <CAJ_ENFEr-dzpZuDFfXrOD5XLOMUj80JkjK9Br5opzaqOEawqNg@mail.gmail.com> (raw)
In-Reply-To: <87vbeh3wa9.wl-jch@pps.univ-paris-diderot.fr>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
They say "connection" but really mean a "state". Handshake completed or
not, a state must be created. Most torrent clients also self limit the
number of "half opened" connections, as not to kill your $200 firewall with
a flood of new states. I've seen a default of between 10 and 50.
On Sun, Jun 21, 2015 at 10:39 AM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:
>
>> https://torrentfreak.com/popular-torrents-being-sabotaged-by-ipv6-peer-flood-150619/
>>
>
> That's really strange — it looks like µTorrent is using up a connection
> slot even before the peer has performed the µTP three-way handshake.
>
> -- Juliusz
>
>
[-- Attachment #2: Type: text/html, Size: 1338 bytes --]
next prev parent reply other threads:[~2015-06-21 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 16:01 Dave Taht
2015-06-19 22:14 ` Benjamin Cronce
2015-06-20 1:08 ` Dave Taht
2015-06-20 0:47 ` Dave Taht
2015-06-21 15:39 ` Juliusz Chroboczek
2015-06-21 16:24 ` Benjamin Cronce [this message]
2015-06-21 15:32 ` [Bloat] BitTorrent and IPv6 [was: tackling torrent...] Juliusz Chroboczek
2015-06-22 19:29 ` Dave Taht
2015-06-22 21:08 ` Juliusz Chroboczek
2015-06-24 17:30 ` Juliusz Chroboczek
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ_ENFEr-dzpZuDFfXrOD5XLOMUj80JkjK9Br5opzaqOEawqNg@mail.gmail.com \
--to=bcronce@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
/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