Custom Query (97 matches)
Results (21 - 40 of 97)
| Ticket | Summary | Keywords | Status | Owner | Type | Priority |
|---|---|---|---|---|---|---|
| #11625 | Tor DNSPORT returns NXDOMAIN for AAAA records? | tor-client, dns, exit-node-choice, ipv6 | new | defect | Medium | |
| #12138 | No IPv6 support when suggesting a bindaddr to a PT | tor-pt, tor-bridge ipv6 | new | enhancement | Medium | |
| #13112 | Some things are probably broken when we advertise multiple ORPorts and only some are reachable | tor-relay, reachability, self-testing, needs-design, ipv6, tor-bridge, 034-triage-20180328, 034-removed-20180328, teor-unreached-2019-03-08, teor-backlog-revise | needs_revision | defect | Medium | |
| #17013 | Does chutney need to test various rare IPv6/IPv4 combinations? | testing, SponsorS, tor-tests-integration, ipv6 | new | enhancement | Medium | |
| #17230 | Local DNS resolver will not resolve AAAA records with fc00::/8 prefixes. | tor-client tor-relay cjdns ipv6 needs-insight maybe-bad-idea | new | defect | Medium | |
| #17636 | Can a single IPv6 bridge failure stop Tor connecting? | tor-client tor-bridges, ipv6 needs-diagnosis | new | defect | Medium | |
| #17835 | Make ClientPreferIPv6ORPort smarter | tor-client, ipv6, 040-deferred-201915 | assigned | enhancement | Medium | |
| #17845 | Add unit tests for IPv6 relay descriptors | ipv6, tor-tests-coverage, tor-tests-unit, tor-relay | new | enhancement | Medium | |
| #19487 | Meek and ReachableAddresses | ipv6, bridges, pluggable-transports, regression, 032-unreached, meek | needs_revision | defect | Medium | |
| #20067 | Chutney should verify IPv6 SOCKSPorts | testing, ipv6 | new | enhancement | Medium | |
| #20068 | Chutney tests for IPv6-only bridge clients | ipv6 | new | defect | Medium | |
| #20218 | Fix and refactor and redocument routerstatus_has_changed | ipv6, 029-proposed, tor-control, easy, spec-conformance, review-group-31, 034-triage-20180328, 034-removed-20180328 | needs_revision | defect | Medium | |
| #21043 | Make ClientUseIPv4 and ClientUseIPv6 equivalent to ReachableAddresses | ipv6, tor-client reachableaddresses torrc configuration | new | defect | Medium | |
| #21310 | Exits should tell clients when they are connecting to an IPv6-only hostname | ipv6, 034-triage-20180328, 034-removed-20180328 | needs_revision | defect | Medium | |
| #21311 | Exits should resolve IPv6 addresses, regardless of IPv6Exit | ipv6, 031-deferred-20170425, 033-triage-20180320, 033-removed-20180320 | needs_information | defect | Medium | |
| #21355 | Warn when IPv6Exits have no ipv6-policy line in their descriptor | ipv6 easy intro log tor-relay tor-dirauth | new | defect | Medium | |
| #21397 | Tor TransparentProxy documentation: add IPv6 support / port to nftables | tor-doc wiki nftables ipv6 transproxy tor-client | new | enhancement | Medium | |
| #21499 | client_dns_incr_failures while passing not hostname but only IP | tor-client, ipv6, triaged-out-20170308, annoying dns | new | defect | Medium | |
| #21524 | private:* contains valid IPv6 addresses | ipv6 exit-policies tor-relay | new | defect | Medium | |
| #21902 | evdns adds default DNS servers, but chutney wants a consistent environment | chutney-wants, ipv6, tor-relay dns exit testing | new | defect | Medium |
Note: See TracQuery
for help on using queries.
