Opened 5 years ago

Closed 5 years ago

#12831 closed defect (fixed)

Automapped IPv6 range bug.

Reported by: epoch Owned by: massar
Priority: Medium Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version: Tor: 0.2.5.5-alpha
Severity: Keywords: tor-client automap 026-triaged-1
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I get a "Missing mapping for..." error message when using an IPv6 VirtualAddrRange for automapping even through the address shows up when listing address mappings from the control port.

Child Tickets

Change History (8)

comment:1 Changed 5 years ago by epoch

I followed the error message to connection_edge.c. socks->address contains square brackets which, if stripped out at the beginning of the function with the error message, causes automapping for IPv6 to work.

comment:2 Changed 5 years ago by nickm

Keywords: tor-client automap added
Milestone: Tor: 0.2.???Tor: 0.2.6.x-final
Priority: minornormal

comment:3 Changed 5 years ago by nickm

Can you give an exact set of steps to reproduce this?

comment:4 Changed 5 years ago by nickm

Keywords: 026-triaged-1 added

comment:5 Changed 5 years ago by teor

Keywords: tor-client, automap, 026-triaged-1tor-client automap 026-triaged-1
Milestone: Tor: 0.2.6.x-finalTor: 0.2.7.x-final
Owner: set to massar
Status: newassigned

comment:6 Changed 5 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.6.x-final

Actually, I'd really like automapping to work in 0.2.6 if at all possible. It enables a large class of nice configurations.

comment:7 Changed 5 years ago by nickm

Did the fix I just merged for #13811 fix this?

comment:8 Changed 5 years ago by nickm

Resolution: fixed
Status: assignedclosed

My testing suggests this is fixed.

Note: See TracTickets for help on using tickets.