[metrics-team] Where do the by-transport counts come from in userstats-bridge-combined?

David Fifield david at bamsoftware.com
Fri Sep 22 20:05:21 UTC 2017


On Sun, Jun 04, 2017 at 05:00:24PM +0200, Karsten Loesing wrote:
> >> If you think the result will be interesting for Metrics website
> >> visitors, would you want to start working on a similar patch?
> > 
> > My immediate goal is just to be able to compare the IPv4 and IPv6 usage
> > of a single bridge, one of the default obfs4 bridges, the only one that
> > has an IPv6 address: https://bugs.torproject.org/22429. I was originally
> > going to ask the operator to use a separate fingerprint for IPv4 and
> > IPv6, to make it easier, but then I thought that it would be possible to
> > get bounds using the existing statistics. It looks like for this, all I
> > have to do is look at the ratio of v4 and v6 in bridge-ip-versions.
> > 
> > And, it looks like Onionoo already does what I was thinking of:
> > https://onionoo.torproject.org/clients?fingerprint=D9C805C955CB124D188C0D44F271E9BE57DE2109
> > 	"versions":{"v4":0.9999944}
> 
> This is correct.
> 
> Note that we're considering to remove this field in Onionoo, because
> you're probably the first person who found (and publicly stated) that
> this is useful information. ;)
> 
> https://trac.torproject.org/projects/tor/ticket/22033
> 
> But you can always look at bridge-ip-versions lines and learn this
> information, as you did here, so you don't really need Onionoo for this.

I made a graph of bridge-ip-versions for the bridge in question. Nothing
too surprising, though there is a bump in August 2017 I don't have an
explanation for.

https://bugs.torproject.org/22429#comment:7


More information about the metrics-team mailing list