Opened 3 years ago

Last modified 6 months ago

#20068 new 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:


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 (8)

comment:1 Changed 3 years ago by teor

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

comment:2 Changed 3 years ago by teor

We should also test with:

ClientUseIPv6 1
ClientPreferIPv6ORPort 1


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 3 years ago by teor

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

comment:4 Changed 22 months ago by teor

Sponsor: SponsorV-can

comment:5 Changed 22 months ago by teor

Owner: teor deleted
Status: newassigned

comment:6 Changed 17 months ago by teor

Status: assignednew

Make everything that is assigned to no-one new again.

comment:7 Changed 6 months ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:8 Changed 6 months ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Note: See TracTickets for help on using tickets.