#29570: Enforce mutually exclusive logic for IPv6 ORPort flags
-------------------------------------------------+-------------------------
Reporter: s7r | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version: Tor:
| unspecified
Severity: Normal | Resolution:
Keywords: tor-relay, ipv6, reachability, | Actual Points:
needs-proposal |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by AVee):
Replying to [comment:12 neel]:
> Replying to [comment:10 AVee]:
> * Add overhead to IPv6 connections as they would be routed to IPv4. On
top of this, you won't really have true IPv6 sockets as much as IPv4
sockets routed to an IPv6 address.
Agreed, although the actual impact of this overhead depends on a lot of
factors. If done correctly the impact can be minimal. Note that the same
is true for IPv4 portforwarding, which we all accept as a valid way of
making a node reachable.
> * Possibly make the consensus harder to calculate with a non-standard
configuration.
I assume that's not the case. For the outside world it doesn't work or
look any different, so as such it should not have any impact outside of
the configuration of the node itself. Again, this is not different from
IPv4 portforwarding.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29570#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
