diff options
| author | teor <teor@torproject.org> | 2020-02-04 14:16:17 +1000 |
|---|---|---|
| committer | teor <teor@torproject.org> | 2020-02-05 22:03:33 +1000 |
| commit | f090a2233c9180df6b606c1b598fe72a1ae5441c (patch) | |
| tree | 3755c408fc0f2d5e12f4a7f97cd1d5d8742e141a /proposals/312-relay-auto-ipv6-addr.txt | |
| parent | fd4716f1ce976c41662046f1022c2546d993c8a2 (diff) | |
| download | torspec-f090a2233c9180df6b606c1b598fe72a1ae5441c.tar.gz torspec-f090a2233c9180df6b606c1b598fe72a1ae5441c.zip | |
Prop 312: Explain address resolution using sockets
As suggested by Nick Mathewson.
Part of 33073.
Diffstat (limited to 'proposals/312-relay-auto-ipv6-addr.txt')
| -rw-r--r-- | proposals/312-relay-auto-ipv6-addr.txt | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/proposals/312-relay-auto-ipv6-addr.txt b/proposals/312-relay-auto-ipv6-addr.txt index 98306c7..3209e0b 100644 --- a/proposals/312-relay-auto-ipv6-addr.txt +++ b/proposals/312-relay-auto-ipv6-addr.txt @@ -101,7 +101,7 @@ Ticket: #33073 1. the Address torrc option 2. the address of the hostname (resolved using DNS, if needed) 3. a local interface address - (by making a self-connected socket, if needed) + (by making an unused socket, if needed) 4. an address reported by a directory server (using X-Your-Address-Is) When using the Address option, or the hostname, tor supports: @@ -147,7 +147,7 @@ Ticket: #33073 1. the Address torrc option 2. the advertised ORPort address 3. a local interface address - (by making a self-connected socket, if needed) + (by making an unused socket, if needed) 4. the address of the host's own hostname (resolved using DNS, if needed) 5. an address reported by a directory server (using X-Your-Address-Is) @@ -275,10 +275,11 @@ Ticket: #33073 online, except for short quotes (see [getaddrinfo man page] for the relevant quote). - If the local interface addresses are unavailable, tor opens a self-connected - UDP socket to a publicly routable address, but doesn't actually send any - packets. Instead, it uses the socket APIs to discover the interface address - for the socket. + If the local interface addresses are unavailable, tor opens a UDP socket to + a publicly routable address, but doesn't actually send any packets. + Instead, it uses the socket APIs to discover the interface address for the + socket. (UDP is used because it is stateless, so the OS will not send any + packets to open a connection.) Relays that use NAT to reach the Internet may have no publicly routable local interface addresses, even on the public tor network. The NAT box has |