From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] BitTorrent and IPv6 [was: tackling torrent...]
Date: Wed, 24 Jun 2015 19:30:53 +0200 [thread overview]
Message-ID: <87d20lau9e.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <87d20nmox1.wl-jch@pps.univ-paris-diderot.fr>
>> It also appeared to show that transmission chose one and only one of the
>> ipv6 addresses available on this box.
> Yes. My code explicitly binds the UDPv6 socket to a single address.
I've just been informed by a reliable source that Vuze's "mldht" plugin
does not suffer from this issue -- it runs a different instance of the
Kademlia algorithm on every address allocated to the host:
"to the outside world it just looks like separate DHT nodes running
on each port. you have to look closely to notice the shared internal
state"
I've also received a copy of the Kademlia routing table of their
implementation running on a host with 256 distinct IPv4 addresses.
-- Juliusz
prev parent reply other threads:[~2015-06-24 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 16:01 [Bloat] tackling torrent on a 10mbit uplink (100mbit down) 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
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 [this message]
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=87d20lau9e.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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