Ticket #33 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

Tor's BandwidthRate doesn't work with Vidalia

Reported by: anonymous Owned by: developer
Priority: trivial Milestone:
Component: Vidalia Version:
Keywords: Cc:

Description

I changed BandwidthRate?-setting in my currently used torcc to 20 KB and Vidalia changed it to 20480. Now when I look my Tor-server's bandwidth usage it goes atleast 60 kb up or down when looking at Vidalia's badwidth-meter. So basicly it doesn't work restrict bandwidth-usage at all.

Change History

Changed 3 years ago by edmanm

  • priority changed from major to trivial
  • status changed from new to closed
  • version 0.0.4 deleted
  • resolution set to invalid
I changed BandwidthRate-setting in my currently used torcc to 20 KB and Vidalia changed it to 20480.

20KB * (1024 bytes/KB) = 20480 bytes

Now when I look my Tor-server's bandwidth usage it goes atleast 60 kb up or down when looking at Vidalia's badwidth-meter. So basicly it doesn't work restrict bandwidth-usage at all.

Please read and understand this and this information.

We will also have better support for doing your own server rate limiting without editing your torrc soon.

Changed 3 years ago by anonymous

Err, I know that a single kilobyte is 1024 bytes not 1000 and that Vidalia changed the 20 kb to bytes but still the restriction doesn't really work if Tor-server downloads at speed 572,74 kb/s and ups at 70 kb/s. So is the bug related to Vidalia or Tor?

Changed 3 years ago by anonymous

  • status changed from closed to reopened
  • resolution invalid deleted

Changed 3 years ago by edmanm

  • status changed from reopened to closed
  • resolution set to invalid

Vidalia did not change anything. Vidalia doesn't even know anything about BandwidthRate? yet. Also, how are you concluding that Vidalia is changing this value?

If there is a bug, it would most likely be in Vidalia. But I don't think there is a bug here; I think you are confused. Again, please read and understand this and this.

If you set your BandwidthRate? at 20KB (note that there is a difference between KB and kb), Tor can still exceed that for periods of high traffic (bursts) depending on what you have BandwidthBurst? set to, as you learned from reading those two FAQ entries to which I have pointed you. Since you haven't mentioned BandwidthBurst? yet, I can only assume you haven't changed it from its default of 5MB.

To quote the FAQ, "BandwidthBurst? is a pool of bytes used to fulfill requests during short periods of traffic above BandwidthRate? but still keeps the average over a long period to BandwidthRate?." For more information, please see this article on token buckets.

Note: See TracTickets for help on using tickets.