<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><span></span></div><div><div></div><div><br></div><div>On 18 Feb 2018, at 11:17, nusenu <<a href="mailto:nusenu-lists@riseup.net">nusenu-lists@riseup.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hello,</span><br><span></span><br><span>I've got two questions regarding some bw related torrc settings.</span><br><span></span><br><span>1) </span><br><span></span><br><span>after reading tor's manpage section about PerConnBWRate:</span><br><blockquote type="cite"><span>PerConnBWRate N</span><br></blockquote><blockquote type="cite"><span>bytes|KBytes|MBytes|GBytes|TBytes|KBits|MBits|GBits|TBits If set, do</span><br></blockquote><blockquote type="cite"><span>separate rate limiting for each connection from a non-relay. You</span><br></blockquote><blockquote type="cite"><span>should never need to change this value, since a network-wide value is</span><br></blockquote><blockquote type="cite"><span>published in the consensus and your relay will use that value.</span><br></blockquote><blockquote type="cite"><span>(Default: 0)</span><br></blockquote><span></span><br><span>I was wondering what value dir auths set in consensus, but I was not </span><br><span>able to find anything that looked like it in consensus [1].</span><br></div></blockquote><div><br></div><div>That's because the directory authorities do not set a value in the</div><div>consensus.</div><br><blockquote type="cite"><div><span>dir-spec [2]</span><br><blockquote type="cite"><span>        "perconnbwrate" and "perconnbwburst" -- if set, each relay sets</span><br></blockquote><blockquote type="cite"><span>        up a separate token bucket for every client OR connectio [...]>         First-appeared: 0.2.2.7-alpha</span><br></blockquote></div></blockquote><div><br></div><div>This line is not accurate - the perconn* code still exists in Tor master:</div><br><blockquote type="cite"><div><blockquote type="cite"><span>        Removed-in: 0.2.2.16-alpha</span></blockquote></div></blockquote><div><br></div><div><a href="https://gitweb.torproject.org/tor.git/tree/src/or/connection_or.c#n763">https://gitweb.torproject.org/tor.git/tree/src/or/connection_or.c#n763</a></div><div><br></div><div>We should document the tor versions that implement consensus</div><div>parameters. There's no point documenting when the parameters were</div><div>present in the consensus. </div><br><blockquote type="cite"><div><span>Does that mean that dir auths stopped including it since tor 0.2.2.16-alpha</span><br><span>should we update the manpage then?</span><br></div></blockquote><div><br></div><div>Yes, we should update the man page so it doesn't say that the</div><div>value is in the consensus.</div><br><blockquote type="cite"><div><span>Is there a default value if consensus does not say anything about it </span><br><span>or is there no per connection limit in that case?</span><br></div></blockquote><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">The default is BandwidthRate/Burst. This should also be in the man</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">page.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Please feel free to open a ticket in Core Tor, 0.3.4.</span></div><br><blockquote type="cite"><div><span>2)</span><br><span>Is there a RelayBandwidthRate torrc setting in addition to BandwidthRate</span><br><span>so tor instances which act as clients and relays at the same time can</span><br><span>have independent bw rates for each role (client, relay)?</span><br><span></span><br><span>BandwidthRate -> affects client and relay role</span><br><span>RelayBandwidthRate -> affects only relay role</span><br><span>is this correct?</span><br></div></blockquote><div><br></div><div>Yes.</div><div><br></div><div>But it's slightly more complicated: when an OR connection is used</div><div>for client purposes (like downloading a consensus), all its cells are</div><div>counted as client bandwidth for the next 30 seconds.</div><div><br></div><div>T</div><br><blockquote type="cite"><div><span>[1] <a href="https://collector.torproject.org/recent/relay-descriptors/consensuses/2018-02-17-23-00-00-consensus">https://collector.torproject.org/recent/relay-descriptors/consensuses/2018-02-17-23-00-00-consensus</a></span><br><span></span><br><span>[2] <a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1847">https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1847</a></span><br></div></blockquote></div></body></html>