Opened 6 months ago

Last modified 2 months ago

#28057 new enhancement

When randomly choosing IPv4 or IPv6, log better IPv6 preference info

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client, ipv6, postfreeze-ok, 040-deferred-20190220
Cc: neel@… Actual Points:
Parent ID: #17835 Points:
Reviewer: Sponsor:

Description

connection_connect_log_client_use_ip_version() logs an info-level message when ClientPreferIPv6ORPort isn't satisfied:
https://github.com/torproject/tor/blob/df2b46d18c4a3d6e5eb364f80111ef6c7811383c/src/core/mainloop/connection.c#L2019

We should update it for ClientAutoIPv6ORPort.

Child Tickets

Change History (4)

comment:1 Changed 5 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:2 Changed 5 months ago by teor

Type: defectenhancement

comment:3 Changed 3 months ago by nickm

Keywords: postfreeze-ok added

Mark some tickets as postfreeze-ok, to indicate that I think they are okay to accept in 0.4.0 post-freeze. Does not indicate that they are all necessary to do postfreeze.

comment:4 Changed 2 months ago by nickm

Keywords: 040-deferred-20190220 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.

Note: See TracTickets for help on using tickets.