[tor-bugs] #23761 [Metrics/Website]: Add IPv6 relay graphs to metrics site
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Nov 8 10:21:47 UTC 2017
#23761: Add IPv6 relay graphs to metrics site
Reporter: teor | Owner: metrics-team
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Metrics/Website | Version:
Severity: Normal | Resolution:
Keywords: core-tor-wants, ipv6 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
Changes (by teor):
* cc: isis (added)
Hi Karsten, thanks, these look great!
Replying to [comment:4 karsten]:
> Alright, here's a first graph:
> This graph shows various metrics of IPv6-capable relays over the past
> - Going through the different line colors, the red line ("announced")
includes all relays or bridges that put an IPv6 address into their server
descriptor that they upload to the directory authorities or bridge
> - The green line ("confirmed") only includes relays with IPv6 OR ports
that the directory authorities found reachable and that they included in
the votes and then the consensus. There is no green line for bridges,
because the bridge authority either does not perform IPv6 reachability
tests or does not include confirmed IPv6 addresses in its status.
> - The cyan line ("exiting") stands for relays claiming in their server
descriptor that they permit IPv6 exiting to at least one TCP port.
> - The purple line ("missing") is only there for a technical reason, to
show when we're missing server descriptors that are referenced from
consensuses or bridge network statuses, which leads to us not knowing
about the green or purple line. I'm yet unsure what to do in such cases.
> - Going through the graphs from top to bottom, cw_frac stands for
consensus weight fraction. Note that this is a relay-only graph, just like
the next few graphs.
> - The next three show guard/middle/exit probability of relays, which is
consensus weight plus bandwidth weights like: `Wgg - Weight for Guard-
flagged nodes in the guard position`.
> - The next two, relay_frac and bridge_frac, show the fraction of relays
and bridges in numbers, and the last two, relays and bridges, show the
> A few conclusions:
> - Note the change towards the end of October when red and green lines
converged. I believe that's related to the directory authorities fixing
Yes. They'll appreciate seeing this change.
And this means we should keep both the announced and confirmed lines, so
we can check if they diverge again.
> - It's interesting that a higher fraction of relays in terms of exit
probability permits exiting than has an announced or confirmed working
IPv6 OR port. I didn't check in detail whether all relays with non-reject-
all exit policy have a working IPv6 OR port.
Exiting is easy to configure, and works even if you have a dynamic IPv6
ORPorts need to be static and known at config time. We're working on
making them easier.
> Which of these graphs should we put on the Tor Metrics website? Note
that this visualization shows 4 * 8 = 32 data sets, and there's no way we
can put then all on the website, not even when combining some of them in
one graph. We can easily pick two or three graphs, possibly with multiple
lines in them, but we can't do more. Of course we can make the full CSV
file available, so that people can make their own special graphs quite
I would like to see a relay counts by IPv6 announced OR / IPv6 confirmed
OR / IPv6 exiting / total (IPv4) OR. It would seem to fit with the other
graphs on the servers page of metrics. I want to have these numbers
because they are a useful overview, and because they affect things like
the size of the consensus.
I would also like to see advertised bandwidth by confirmed guard IPv6 OR /
confirmed middle IPv6 OR / confirmed exit IPv6 OR / IPv6 exiting / total
(IPv4) OR. This could go with the other graphs on the traffic page of
metrics. I want to have these numbers because they show us how easy it is
for clients to use IPv6 to get in and out of the Tor Network, and they can
help us decide when we can use more IPv6 between relays. (I don't want to
graph observed bandwidth until we start logging separate IPv4 and IPv6
stats on ORPorts and exits, because I think it would be confusing.)
I've cc'd isis, because they will have a better idea of which IPv6 bridge
stats would be useful. (I'd say "like the existing bridge stats", or "like
the IPv6 relay stats", but I'd only be guessing.)
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23761#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs