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

Re: Questions about gathering information and statistics about the tor-network

On Sun, 18 Jan 2009 13:17:17 +0100
Karsten Loesing <karsten.loesing@xxxxxxx> wrote:

> Starting with the descriptors is a good idea. You can collect them with
> Peter Palfrader's directory archive scripts in the contrib/ directory.

I already created my own one :)

> Right, making data available might turn out to be difficult. I haven't
> looked at specific frameworks, yet. One option would be to integrate
> more graphics into TorStatus (http://trunk.torstatus.kgprog.com/).
> Kasimir Gabert did a great job displaying bandwidth histories for the
> past day, week, month, and so on. Maybe these graphics can be extended,
> given that we have good data to present.

Yes but there are so many links you can make between different informations, you can't show them all on one page. I think a dynamicaly solution like giving one the possibilty to say: show me one single graph with the development of all exitnodes at all and all exitnodes in britain between this dates, would be pretty cool. If stator's ready does everything on the console and with gnuplot which I want I'm going to look further into this.
> Ah, the exam phase? :) If so, good luck with that!

Thanks ;)

Before I leave you for my books I wanna show you what my tool (called stator, written in ruby) does so far.

It's divided in two main parts:
 - an api for connecting and talking with the controlport
 - an api for requesting and evaluating server-descriptors

As soon as it can be used by others I will make a public release of it. At the moment both apis need way more coding work to be used by others than me and aren't documented at all.

I spent most of the work so far on catching the data and creating useable data-structures to be able to make all links between different informations one wants to have. The server-descriptor api at the moment is able (next to creating the datastructure: an array of hashes of the single routers) to take a single-property like 'entrynodes' or an array ['Germany','France'] and returns the number of routers which have those properties. Next when I have time this will be extended to accept an array of arrays of properties like [['Germany','entrynodes'],['France','entrynodes'],['USA','exitnodes']]..to show the number of routers which have all properties of one array at the same time. 

In the attachment you see some output of a programm using these apis at the moment. It's a request for all property values which different routers have and the number of routers which have this value. It's structured like this:


while $PROPERTY is in this order
- typ
- OS
- Country
- Tor-Version
- uptime
- bandwidth_avg of a router

blocked_ports of exitnodes is still work in progress because I haven't found the time to handle ranges in a good way...


Attachment: output
Description: Binary data

Attachment: signature.asc
Description: PGP signature