[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #23761 [Metrics/Website]: Add IPv6 relay graphs to metrics site



#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:
----------------------------------+------------------------------

Comment (by karsten):

 Alright, here's a first graph:

 [[Image(servers-ipv6-2017-11-06.png)]]

 This graph shows various metrics of IPv6-capable relays over the past five
 weeks.

 Explanation:

  - 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
 authority.

  - 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
 absolute numbers.

 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
 IPv6 stuff.

  - 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.

 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
 easily.

 By the way, nusenu, thanks a lot for sharing your OrNetStats above. That
 was quite helpful when starting to write some code here. Cool stuff!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23761#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs