Re: [tor-relays] Emerald Onion's new relays

Subject: Re: [tor-relays] Emerald Onion's new relays

Date: Tue, 13 Aug 2019 07:39:21 +1000

Delivery-date: Mon, 12 Aug 2019 17:39:39 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1565645966; bh=TvkWmkn+7QSzfnHedDDmjv51ZkGtjgmRJ6YHR9jV3uI=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=ntrH7jww5BeCxf8MXgmJ7FJE0YAMr8+oWNQAOOw9QpTU7ESJDDHCNcFfcw4hNqy62 2PPUid+Js2CQjv4VRvYl4G6LZRfR36fTbjAudA9qeWHBV8Tk+RRW5rN2ye1IrZp5X0 CILQ216TrDr1kC6JOOV7xSDnHHgHlVOOOTyC12Cs=

In-reply-to: <20190813000819.334557d7@natsu>

List-archive: <http://lists.torproject.org/pipermail/tor-relays/>

List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

List-post: <mailto:tor-relays@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>

References: <BN8PR19MB275621999383793C67E71923C5560@BN8PR19MB2756.namprd19.prod.outlook.com> <4a09597e-6004-2904-3778-4fca260086d8@riseup.net> <CACiAZpgXcAwiCZq7y099YHSxc66fm_xYBWakUfwXpetUqcU8og@mail.gmail.com> <CAD2Ti29nACAi43b6esmMM-HdRyGBsw_=_QXWt-HyvUr34rg97g@mail.gmail.com> <MWHPR19MB01602B374DF0C739E78C0D68C5D30@MWHPR19MB0160.namprd19.prod.outlook.com> <20190813000819.334557d7@natsu>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

Hi,

On 13 Aug 2019, at 05:08, Roman Mamedov <rm@xxxxxxxxxxx> wrote:

On Mon, 12 Aug 2019 00:46:50 +0000
Christopher Sheats <yawnbox@xxxxxxxxxxxxxxxx> wrote:

Tor Project, please increase your #IPv6 awareness/outreach similar to how
ARIN and the other RIRs try very hard to do.

Before outreach Tor would need some actual IPv6 support, as in using it for
the actual traffic of relay-to-relay communication. I tried running a few
relays with very fast IPv6 and slow IPv4 (due to a common NAT frontend which
was the bottleneck), but it was a complete nonstarter.

Tor relays currently don't connect over IPv6. When 10% of the network

supported IPv6, there wasn't much point, because putting a very small

number of paths over IPv6 has privacy risks. So we focused on client, guard,

and exit IPv6 support.

But currently, about 30% of the consensus weight supports IPv6. So we

are working on a grant for IPv6 support (see below).

We won't be able to prefer IPv6 until 50-67% of relays support IPv6, for

load-balancing and privacy reasons. But we plan on using the

"Happy Eyeballs" (RFC 8305) algorithm on dual-stack relays. So

sufficiently slow IPv4 will cause relays to connect over IPv6. (And we can

tune the load-balancing using the IPv4 to IPv6 delay.)

Tor supports IPv6 very
poorly and nobody cares much.

Lots of us care about IPv6. Our problem is finding *funders* who care enough

to pay for the time we need to implement this complex feature. But we're

working on a grant application right now:

On 12 Aug 2019, at 11:54, teor <teor@xxxxxxxxxx> wrote:

It is discouraging to see so many small and large network operators not using IPv6. Why is this such a problem?

Tor relays don't automatically detect IPv6 addresses, and they don't test the reachability of IPv6 ORPorts. We are working on a grant application to add this support in Tor. (It's more complex than it seems, because we need to split the reachability checks per-ORPort, and add IPv6 extend support to Tor relays.)

Tor Project, please increase your #IPv6 awareness/outreach similar to how ARIN and the other RIRs try very hard to do.

I'll add an awareness objective to our grant application.

_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays