Opened 5 years ago

Last modified 7 months ago

#17011 assigned defect

chutney doesn't verify using IPv6 addresses

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


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

#17013newDoes chutney need to test various rare IPv6/IPv4 combinations?Core Tor/Chutney
#17090closedchutney triggers tor warnings about ExitRelay not being setCore Tor/Chutney
#17812closedChutney tests for IPv6-only clientsCore Tor/Chutney
#20067assignedMrSquancheeChutney should verify IPv6 SOCKSPortsCore Tor/Chutney
#20068assignedChutney tests for IPv6-only bridge clientsCore Tor/Chutney
#20142assignedMrSquancheechutney IPv6 HiddenServicePort testsCore Tor/Chutney
#21001closedteorTest that recent tor clients can use microdescriptors when configured to only use IPv6Core Tor/Chutney
#26664newWhen an exit tells a client about an IPv6-only hostname, the client should choose another IPv6 exitCore Tor/Tor
#30182assignedIPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6Core Tor/Chutney
#31543assignedAdd unit tests or chutney tests for IPv6TrafficCore Tor/Tor

Change History (10)

comment:1 Changed 5 years 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 5 years 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 5 years ago by teor

Keywords: ipv6 added
Parent ID: #16949#17811
Severity: Normal

comment:4 Changed 4 years ago by nickm

Keywords: tor-tests-integration added
Sponsor: SponsorS-can

comment:5 Changed 4 years ago by nickm

Points: 3

comment:6 Changed 4 years ago by nickm

Owner: nickm deleted
Status: newassigned

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

comment:7 Changed 4 years ago by nickm

Status: assignednew

comment:8 Changed 8 months ago by teor

Keywords: outreachy-ipv6 added; SponsorS removed
Sponsor: SponsorS-can

comment:9 Changed 7 months ago by MrSquanchee

Owner: set to MrSquanchee
Status: newassigned

comment:10 Changed 7 months ago by teor

Owner: MrSquanchee deleted

We haven't selected a GSOC or Outreachy applicant yet.

To be fair to all applicants, we should only assign tickets to people who are actively working on that ticket.

Note: See TracTickets for help on using tickets.