Opened 22 months ago

Last modified 13 months ago

#17011 new defect

chutney doesn't verify using IPv6 addresses

Reported by: teor Owned by:
Priority: High Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: SponsorS, testing, ipv6, tor-tests-integration
Cc: Actual Points:
Parent ID: #17811 Points: 3
Reviewer: Sponsor: SponsorS-can

Description

Even when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.

When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.

This is a significant coverage gap that I think is easily fixed by slight modifications to the chutney templating and verification code.

Child Tickets

TicketSummaryOwner
#17013Does chutney need to test various rare IPv6/IPv4 combinations?
#17090chutney triggers tor warnings about ExitRelay not being set
#17812Chutney tests for IPv6-only clients
#20067Chutney should verify IPv6 SOCKSPortsteor
#20068Chutney tests for IPv6-only bridge clientsteor
#20142chutney IPv6 HiddenServicePort teststeor
#21001Test that recent tor clients can use microdescriptors when configured to only use IPv6teor

Change History (7)

comment:1 Changed 22 months ago by teor

To clarify, this most likely means that:

  • the bridges are listening on IPv6, but the bridge clients are connective over IPv4
  • the exits are willing to connect via IPv6, but never get an IPv6 request (but see #16971, an exit on a network where there is no IPv6 DNS may refuse IPv6 requests)

comment:2 Changed 22 months ago by teor

If we are trying to force IPv6-only exit connections, we need to stop the authorities being exits in #17090.

comment:3 Changed 19 months ago by teor

  • Keywords ipv6 added
  • Parent ID changed from #16949 to #17811
  • Severity set to Normal

comment:4 Changed 13 months ago by nickm

  • Keywords tor-tests-integration added
  • Sponsor set to SponsorS-can

comment:5 Changed 13 months ago by nickm

  • Points set to 3

comment:6 Changed 13 months ago by nickm

  • Owner nickm deleted
  • Status changed from new to assigned

Remove myself as chutney ticket owner. Default owners are trouble.

comment:7 Changed 13 months ago by nickm

  • Status changed from assigned to new
Note: See TracTickets for help on using tickets.