Opened 21 months ago

Last modified 3 months ago

#20068 assigned defect

Chutney tests for IPv6-only bridge clients

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: ipv6
Cc: Actual Points:
Parent ID: #17011 Points: 1
Reviewer: Sponsor: SponsorV-can

Description

I think this is working already, but we should check that chutney bridge clients are using IPv6, and not falling back to IPv4.

Child Tickets

Change History (5)

comment:1 Changed 21 months ago by teor

Setting ClientUseIPv4 0 should do this, but we should actually check we're connecting over IPv6.

comment:2 Changed 21 months ago by teor

We should also test with:

ClientUseIPv6 1
ClientPreferIPv6ORPort 1

and

ClientUseIPv6 1
ClientPreferIPv6ORPort 0

in combination with the IPv4 and IPv6 bridge lines, and only an IPv6 bridge line (this will likely require more chutney config variables that say "emit IPv4 bridge lines" and "emit IPv6 bridge lines", both defaulting to true).

comment:3 Changed 16 months ago by teor

Component: Core Tor/TorCore Tor/Chutney
Owner: set to teor

comment:4 Changed 3 months ago by teor

Sponsor: SponsorV-can

comment:5 Changed 3 months ago by teor

Owner: teor deleted
Status: newassigned
Note: See TracTickets for help on using tickets.