Chutney should verify IPv6 SOCKSPorts

Trac:
Description: Chutney will soon verify using client to relay IPv6, but verify only sends traffic to and from tor over IPv4.

We need to test the following:

to

Chutney will soon verify using client to relay IPv6, but verify only sends traffic to and from tor over IPv4.

We need to test the following:

Trac:
Parent: N/A to #17011 (moved)

Trac:
Keywords: N/A deleted, testing, ipv6 added

Trac:
Summary: Chutney should verifyIPv6 SOCKSPorts and IPv6 Exit traffic to Chutney should verify IPv6 SOCKSPorts and IPv6 Exit traffic

The exit part of this has been implemented: chutney has performed IPv6-only exit tests for a while now.

Trac:
Description: Chutney will soon verify using client to relay IPv6, but verify only sends traffic to and from tor over IPv4.

We need to test the following:

to

Chutney will soon verify using client to relay IPv6, but verify only sends traffic to and from tor over IPv4.

We need to test the following:

IPv6 SOCKSPorts,
IPv4 and IPv6 SOCKSPorts with IPv6Traffic, and
~~IPv6 Exits~~
Hidden Services connecting to CHUTNEY_LISTEN_ADDRESS_V6:LISTEN_PORT
Summary: Chutney should verify IPv6 SOCKSPorts and IPv6 Exit traffic to Chutney should verify IPv6 SOCKSPorts

Disowning tickets I don't intend to work on in the next 6 months.

Trac:
Owner: teor to N/A
Status: new to assigned

Mark all tickets that are assigned to nobody as "new".

Trac:
Status: assigned to new

Replying to teor:

The exit part of this has been implemented: chutney has performed IPv6-only exit tests for a while now.

But ipv6-exit doesn't seem to be testing IPv6 traffic, see #30182 (moved).

Trac:
Status: new to assigned
Owner: N/A to MrSquanchee

Marking actively worked on ticket as outreachy-ipv6.

Trac:
Keywords: N/A deleted, outreachy-ipv6 added

changed time estimate to 8h

mentioned in issue #30182 (moved)

Child items ...