#20996: IPv6-only client fails to bootstrap on microdescriptor fetch/fallback ---------------------------------------------+----------------------------- Reporter: mtigas | Owner: Type: defect | Status: | needs_review Priority: High | Milestone: Tor: | 0.3.0.x-final Component: Core Tor/Tor | Version: Tor: | 0.2.8.5-rc Severity: Normal | Resolution: Keywords: ipv6, fallback, review-group-14 | Actual Points: Parent ID: | Points: 0.5 Reviewer: nickm | Sponsor: ---------------------------------------------+-----------------------------
Comment (by teor): Replying to [comment:10 nickm]: > I still don't understand this part: > > I have a question, though: why are we changing the semantics of ClientPreferIPv6*Port ...? > > That is, _why_ are we making it so "PreferIPv6" implies "UseIPv6"? Because otherwise, we won't actually look for IPv6 directory servers, even if IPv6 is preferred. > And should we make corresponding changes in the manpage and in the note the change in the changes file? The manual page doesn't need a change: it already implies that setting ClientPreferIPv6ORPort means we might actually use IPv6. The corresponding changes file entry is: {{{ - Make IP6-using clients try harder to find an IPv6 directory server. Fixes bug 20999; bugfix on 77a9de0 from 17840 in 0.2.8.2-alpha. }}} -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20996#comment:11> 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