From 8af14dea81a2a39be2cb1f76a99a364827ec9d4e Mon Sep 17 00:00:00 2001 From: teor Date: Tue, 11 Feb 2020 14:11:09 +1000 Subject: Prop 312: Clarify IPv6 ORPort Binding Part of 33049. --- proposals/312-relay-auto-ipv6-addr.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'proposals/312-relay-auto-ipv6-addr.txt') diff --git a/proposals/312-relay-auto-ipv6-addr.txt b/proposals/312-relay-auto-ipv6-addr.txt index 98c86c1..ba2ffcc 100644 --- a/proposals/312-relay-auto-ipv6-addr.txt +++ b/proposals/312-relay-auto-ipv6-addr.txt @@ -558,6 +558,12 @@ Ticket: #33073 IP address (in a single API call). Tor should support both styles of networking API. + In particular, if binding to all IPv6 addresses fails, relays should still + try to discover their public IPv6 address, and check the reachability of + that address. Some OSes may not support the IPV6_V6ONLY flag, but they may + instead bind to all addresses at runtime. (The tor install may also have + compile-time / runtime flag mismatches.) + If both reachability checks succeed, relays should publish their IPv4 and IPv6 ORPorts in their descriptor. -- cgit v1.2.3-54-g00ecf