2. Analysis (Mar 2018)¶
2.1. Existing software¶
torflow
: torflow in detailbwscanner
: bwscannerpeerflow
: [PeerflowPaper]bridge bw scanner: [BridgeBwScanner]
OnionPerf
[OnionperfCode]
2.2. Possible approaches¶
Based on the discussions in [mlBwProgressDec1] and [BwAuthRome]:
Develop
peerflow
and deploy it in place oftorflow
Finalize
bwscanner
and deploy in place oftorflow
Adapt the bridge bw scanner that is currently being developed
Adapt
OnionPerf
Path
torflow
Something simple from scratch
Evaluation:
Peerflow
can be developed in parallel, it does not implement the simple algorithm needed in a short termbwscanner
can be fixed and finished but seems hard to mantainThe bridge scanner is considered not suitable for converting into a bandwith scanner
OnionPerf
uses Stem, it would be better to use Stem directly because OnionPerf implements other stuff not needed for the bandwith scannerPatching
torflow
is not considered acceptable because is hard to run and maintainSomething simple from scratch can be implemented reusing
bwscanner
andtxtorcon
new features