Opened 14 months ago

Last modified 8 months ago

#21003 new defect

extend_info_describe should list IPv6 address (if present)

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: easy intro ipv6 logging
Cc: Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:

Description (last modified by teor)

When running an IPv6-only client using:

src/or/tor ClientUseIPv4 0 DataDirectory `mktemp -d` UseMicrodescriptors 0

I get log messages like
[info] add_an_entry_guard(): Chose $906933A309F15D7CF379127078A6791DF9B0C763~Unnamed at 91.121.82.25 as new entry guard

But I'm really contacting them on their IPv6 address. So we should list it along with the IPv4 address.

Child Tickets

Change History (4)

comment:1 Changed 14 months ago by teor

Description: modified (diff)

comment:2 Changed 14 months ago by teor

(This only makes sense for entry nodes: (directory) guards, bridges, fallbacks, authorities - all other relays are referred to by their IPv4 addresses.)

Last edited 13 months ago by teor (previous) (diff)

comment:3 Changed 13 months ago by teor

This is a problem with the address chosen by the calling code: an extend_info only has one tor_addr_t in it.

comment:4 Changed 8 months ago by nickm

Keywords: logging added
Note: See TracTickets for help on using tickets.