[tor-project] Analyzing bwauth disagreements
Donncha Ó Cearbhaill
donncha at donncha.is
Tue Oct 10 17:59:00 UTC 2017
Respect to all people keeping torflow alive.
> There has been a small amount of volunteer progress on maintaining
> the current bandwidth authority code.
> But we haven't made any progress on bwscanner. Perhaps because we're
> not sure who is working on it or where it is at.
> To make progress, we need a list of priorities for bandwidth
> authorities, and people with time to make them happen. This needs
> people from the network team, and directory authority operators.
I haven't spent any time working on the bwscanner code in the past year,
and so my memory of the outstanding issues is a bit hazy.
IIRC the scanning component should be basically functional. It builds
circuits, fetches files and outputs the results into a directory as JSON.
There is probably some work needed on the code to turn these JSON files
into measurements that are readable by the bwauths. I ported the torflow
measurement aggregation code to Stem and it **should** work to generate
bwauth compatible measurement files
That script should be tested to make sure the result look sensible and
actually match the torflow spec.
I think the best thing would be for someone to take the existing
bwsacanner code and just get it running somewhere and start generating
measurements on the real network. It will be the quickest way to find
any issues with the measurement code or aggregation tools.
There are some short instructions in the README about how to collect
measurements and then aggregate those measurements into bwauth files.
Anyone is welcome to contact me with questions. I'm happy to assist in
any way I can.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 659 bytes
Desc: OpenPGP digital signature
More information about the tor-project