Hello,
I'm using tor 0.2.3.25 from Debian Wheezy, the exit policy is recject *.*, I'm not using the node myself.
arm shows these actual bandwidths:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s): Download (13.9 Mb/sec - avg: 11.3 Mb/sec, total: 211.9 GB): Upload (16.0 Mb/sec - avg: 12.6 Mb/sec, total: 237.9 GB):
This is my related config:
BandwidthRate 5 MB # not set in config BandwidthBurst 10 MB # not set in config RelayBandwidthRate 2 MB # set in config RelayBandwidthBurst 4 MB # set in config
I'm a bit puzzled....
Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Since I'm not using the node for anything else but relaying I except the bandwidth is more or less equal the RelayBandwidth limit I set. But the averages are so much higher than either the BandwidthRate and the RelayBandwidthRate?
What is my problem of understanding here?
Thanks, Florian
B=bytes b=bits
therefore, Your config setting of 2MB = 16mb Your config setting of 4MB = 32mb
On 12/10/2013 5:47 AM, Florian Lindner wrote:
Hello,
I'm using tor 0.2.3.25 from Debian Wheezy, the exit policy is recject *.*, I'm not using the node myself.
arm shows these actual bandwidths:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s): Download (13.9 Mb/sec - avg: 11.3 Mb/sec, total: 211.9 GB): Upload (16.0 Mb/sec - avg: 12.6 Mb/sec, total: 237.9 GB):
This is my related config:
BandwidthRate 5 MB # not set in config BandwidthBurst 10 MB # not set in config RelayBandwidthRate 2 MB # set in config RelayBandwidthBurst 4 MB # set in config
I'm a bit puzzled....
Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Since I'm not using the node for anything else but relaying I except the bandwidth is more or less equal the RelayBandwidth limit I set. But the averages are so much higher than either the BandwidthRate and the RelayBandwidthRate?
What is my problem of understanding here?
Thanks, Florian _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Tue, 10 Dec 2013 06:39:00 -0500 BugZ bugmagnet1@gmail.com wrote:
Your config setting of 2MB = 16mb Your config setting of 4MB = 32mb
"mb" what, millibytes? https://en.wikipedia.org/wiki/Metric_prefix
If you're trying to teach others then at least get it right yourself...
On Tue, 10 Dec 2013, Florian Lindner wrote:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s):
Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Burst is not a rate. Its unit is <amount of data> not <amount of data per time>. So it should be MB or Mb.
Cheers,
Please could someone put that in the torrc file or in the configuration page?
On Tue, 10 Dec 2013, Florian Lindner wrote:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s):
Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Burst is not a rate. Its unit is <amount of data> not <amount of data per time>. So it should be MB or Mb.
Cheers,
| .''`. ** Debian ** Peter Palfrader | : :' : The universalhttp://www.palfrader.org/ | `. `' Operating System | `- http://www.debian.org/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
____________________________________________________________ GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
Why do you claim burst is not a rate?
If the amount of data is not measured relative to time, how is it relevant?
the internal variable is Relay_*Bandwidth*_Burst
Doesn't "bandwidth" infer rate? BW is defined as "a measurement of bit-rate https://en.wikipedia.org/wiki/Bit-rate"
On 12/10/2013 8:25 AM, Peter Palfrader wrote:
On Tue, 10 Dec 2013, Florian Lindner wrote:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s): Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Burst is not a rate. Its unit is <amount of data> not <amount of data per time>. So it should be MB or Mb.
Cheers,
On Wed, 11 Dec 2013 04:14:41 +0000, BugZ wrote: ...
If the amount of data is not measured relative to time, how is it relevant?
the internal variable is Relay_*Bandwidth*_Burst
Doesn't "bandwidth" infer rate?
You'd think, but it doesn't here. The algorithm is as follows: There is a variable that holds the current number of bytes allowed to be transferred.
As long as it is smaller than the next packet to be transferred, the packet is kept waiting.
The variable is decreased by the size of each packet transferred, and is increased by BandwidthRate's value every second(*). It is also limited to BandwidthBurst's value. That means, when BandwidthRate hasn't been used up recently the node may transfer up to BandwidthBurst bytes as fast as it can.
But describing BandwidthBurst as bytes per second is pointless because the burst isn't something that can happen *every* second; the burst just can (or can't, depending on the hardware and values) happen within a single second (or a millisecond).
The BandwidthBurst is simply the amount of bytes the node may transmit at max speed if it hasn't used up the BandwidthRate previously.
Andreas
(*) Or a tenth of the per-second value every tenth of a second, or one every 1/BandwidthRate seconds.
Greetings all, I'm in the process of setting up a few Exits on a Cloud provider here in Iceland (one that I used to work at actually). Since they use Cloudstack it means each address per account gets multiple inbound address per instance and share the same address for outbound traffic. I'm worried that abuse notices will be coming in for this outbound address even though I've got 80 on the exit node's IP showing the standard Tor Exit disclaimer. I've tried to set OutboundBindAddress to the outbound IP using arm but this just causes arm to complain about: "[WARN] Error binding network socket: Cannot assign requested address" Any advice would be appreciated. -J
Am Dienstag, 10. Dezember 2013, 11:47:45 schrieb Florian Lindner:
Hello,
I'm using tor 0.2.3.25 from Debian Wheezy, the exit policy is recject *.*, I'm not using the node myself.
arm shows these actual bandwidths:
Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 48.6 Kb/s): Download (13.9 Mb/sec - avg: 11.3 Mb/sec, total: 211.9 GB): Upload (16.0 Mb/sec - avg: 12.6 Mb/sec, total: 237.9 GB):
This is my related config:
BandwidthRate 5 MB # not set in config BandwidthBurst 10 MB # not set in config RelayBandwidthRate 2 MB # set in config RelayBandwidthBurst 4 MB # set in config
I'm a bit puzzled....
Why is bandwidth limit 16 Mb/s? Why bandwidth burst 32 Mb/s?
Thanks for the clarification. I was not aware that the config uses bytes, while arm uses bits for rates and bytes for totals. I must say I was not really expecting usage of bit/s at this place and deem it inconsistent. Usually I encounter bit/s only only at very low levels, close to the metal, like hardware interfaces (exception: audio streaming rates).
Any chance changing Mb/s to MB/s thoughout arm?
Regards, Florian
tor-relays@lists.torproject.org
-
Andreas Krey -
BugZ -
Florian Lindner -
I -
jason＠icetor.is -
Peter Palfrader -
Roman Mamedov