Opened 7 months ago

Last modified 6 weeks ago

#28888 reopened defect

The Relay Search Results table doesn't show the IPv6 capability of a bridge

Reported by: toralf Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords: easy
Cc: Actual Points:
Parent ID: #24264 Points:
Reviewer: Sponsor:

Description

The ORPort is reachable (tested from another IPv6 system in a different network segment), the torrc looks like:

# torrc
#

SocksPort 0
ORPort auto
ORPort [<snip>]:auto
BridgeRelay 1
Exitpolicy reject *:*

RunAsDaemon 1
ControlPort 9051
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

ContactInfo replace k with c : kontakt @ zwiebeltoralf . de
Nickname zwiebeltoralf3

Log warn file /var/log/tor/warn.log

# for arm
#
DisableDebuggerAttachment 0

The metrics link is: https://metrics.torproject.org/rs.html#details/662D4E4DE2C883625C543DFA3C4EE466899E6C85

Child Tickets

Change History (6)

comment:1 Changed 7 months ago by teor

Component: MetricsMetrics/Relay Search
Parent ID: #24264
Summary: metrics doesn't show the IPv6 capability of a bridgeRelay Search doesn't show the IPv6 capability of a bridge

Here's what needs to happen for a bridge to have an IPv6 address:

  1. The bridge authority needs IPv6. It currently has the ReachableIPv6 flag: https://metrics.torproject.org/rs.html#details/BA44A889E64B93FAA2B114E02C2A279A8555C533
  2. The bridge authority needs to test bridge IPv6 addresses. I don't think Serge does that, see #24264.
  3. The bridge authority needs to put IPv6 addresses in the bridge networkstatus document. I'm pretty sure that's worked in the past.
  4. Relay search needs to display IPv6 when a bridge has an IPv6 address (this ticket).

Related: There are also no IPv6 bridges on bridges.torproject.org , see #26542.

comment:2 Changed 7 months ago by teor

Resolution: fixed
Status: newclosed

Fixed by #24264: metrics now shows "IPv4, IPv6" for this bridge.

comment:3 Changed 7 months ago by toralf

I'd like to re-open this ticket as long as the Search result windows doesn't show the IPv6 capability (eg.: https://metrics.torproject.org/rs.html#search/zwiebeltoralf)

comment:4 Changed 6 months ago by teor

Resolution: fixed
Status: closedreopened
Summary: Relay Search doesn't show the IPv6 capability of a bridgeThe Relay Search Results table doesn't show the IPv6 capability of a bridge

Ok, I'm sure there's just a small amount of missing code to show IPv6 in that table.

comment:5 Changed 5 months ago by gaba

Priority: MediumLow

Low priority for now.

comment:6 Changed 6 weeks ago by irl

Keywords: easy added
Priority: LowMedium

A synthetic flag is needed here to be generated based on the presence of the IPv6 address. My guess is that this code only runs on relays or is looking for a colon after we've already replaced it with the IPv6 string.

Note: See TracTickets for help on using tickets.