[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21272 [Metrics]: Onionperf deployment
#21272: Onionperf deployment
-------------------------+------------------------------
Reporter: hiro | Owner: metrics-team
Type: enhancement | Status: needs_review
Priority: Medium | Milestone:
Component: Metrics | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------+------------------------------
Comment (by karsten):
hiro, I just looked a bit more at the data and found a few differences
that we can work with. For example, OnionPerf randomly picks a file size
(with different weights, though) every five minutes whereas Torperf had
three separate schedules for each file size, which is okay. Also,
OnionPerf alternates between direct download and download via onion
address, which is different from Torperf, but which is okay, too.
However, there's one difference that we should fix: the direct downloads
go to port 8080, not to port 80. The issue is that the set of exits
permitting port 8080 may be different from the set permitting port 80, so
this might impact measurement results. As far as I can see there are two
ways to do this: either run OnionPerf on port 80 (which may have security
implications), or configure a firewall rule to forward port 80 to 8080. I
assume we'll want to do the latter. In that case we'll have to use
OnionPerf's options `--tgen-listen-port` and `--tgen-connect-port` to tell
it where to listen (8080) and where to connect (80).
Would you want to try making that change?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21272#comment:24>
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