#25687: over-report of observed / self-measure bandwidth  on fast hardware --
important to torflow / peerflow
 Reporter:  starlight     |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:

Comment (by teor):

 Replying to [comment:7 starlight]:
 > thank you for the update, bwscanner I presume?

 No, simple bandwidth scanner.
 bwscanner doesn't generate files that authorities can use yet, so I don't
 know if it will use self-reported bandwidths for scanning.

 > I won't spend time quantifying this issue with 0.3.3, at least for now,
 though I did come up with a plan.  If peerflow happens then measurement
 quality is a concern; could spend some time on the aforementioned

 I think there are some inaccuracies we will just have to live with, and
 this might be one of them.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25687#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to