<html><head></head><body><div class="ydp166507d0yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>David,</div><div><br></div><div>Has Tor Metrics implemented your RFC related to Written Bytes per Second and Read Bytes per Second on Onionoo?</div><div><br></div><div>As of<span> the 27th of February, </span>I've noticed a change in reporting that accurately reflects the aggregate of my Tor Relay Nodes opposed to the previously reported Single Tor Node. Are you seeing a similar change for snowflake.torproject.org?</div><div><br></div><div>Additionally, other than the hourly stacktrace errors in the syslog, the secure_onion_key workaround seems to be working well without any ill side-effects. I've been able to operate with the same secure_onion_key for close to 5 weeks, now. Have you run into any issues?</div><div><br></div><div>Thank you for your response.</div><div><br></div><div>Respectfully,</div><div><br></div><div><br></div><div>Gary</div><div class="ydp166507d0signature">—<br>This Message Originated by the Sun.<br>iBigBlue 63W Solar Array (~12 Hour Charge)<br>+ 2 x Charmast 26800mAh Power Banks<br>= iPhone XS Max 512GB (~2 Weeks Charged)</div></div>
<div><br></div><div><br></div>
<div id="ydp166507d0yahoo_quoted_6773358738" class="ydp166507d0yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, February 8, 2022, 11:49:47 PM MST, Gary C. New via tor-relays <tor-relays@lists.torproject.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp166507d0yiv7032496842"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;" class="ydp166507d0yiv7032496842ydpdd05d81eyahoo-style-wrap"><div><div>David,</div><div><br clear="none"></div><div>Excellent Documentation and References!</div><div><br clear="none"></div><div>I hope the proposed RFC's (<span>auth, key, and metrics)</span> for loadbalanced Tor topologies are seriously considered and implemented by Tor Core and Tor Metrics.</div><div><br clear="none"></div><div>Great Work!</div><div><br clear="none"></div><div>Respectfully,</div><div><br clear="none"></div><div><br clear="none"></div><div>Gary</div><div class="ydp166507d0yiv7032496842ydpdd05d81esignature">—<br clear="none">This Message Originated by the Sun.<br clear="none">iBigBlue 63W Solar Array (~12 Hour Charge)<br clear="none">+ 2 x Charmast 26800mAh Power Banks<br clear="none">= iPhone XS Max 512GB (~2 Weeks Charged)</div></div>
<div><br clear="none"></div><div><br clear="none"></div>
<div id="ydp166507d0yiv7032496842yqt66745" class="ydp166507d0yiv7032496842yqt7447743296"><div id="ydp166507d0yiv7032496842ydpdd05d81eyahoo_quoted_4780941010" class="ydp166507d0yiv7032496842ydpdd05d81eyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, February 8, 2022, 10:02:53 AM MST, David Fifield <david@bamsoftware.com> wrote:
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div>The load-balanced Snowflake bridge is running in production since<br clear="none">2022-01-31. Thanks Roger, Gary, Roman for your input.<br clear="none"><br clear="none">Hopefully reproducible installation instructions:<br clear="none"> <a shape="rect" href="https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/Snowflake-Bridge-Installation-Guide?version_id=6de6facbb0fd047de978a561213c59224511445f" rel="nofollow" target="_blank">https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Guides/Snowflake-Bridge-Installation-Guide?version_id=6de6facbb0fd047de978a561213c59224511445f</a><br clear="none">Observations since:<br clear="none"> <a shape="rect" href="https://bugs.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/40095#note_2774428" rel="nofollow" target="_blank">https://bugs.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/40095#note_2774428</a><br clear="none"><br clear="none">Metrics graphs are currently confused by multiple instances of tor<br clear="none">uploading descriptors under the same fingerprint. Particularly in the<br clear="none">interval between 2022-01-25 and 2022-02-03, when a production bridge and<br clear="none">staging bridge were running in parallel, with four instances being used<br clear="none">and another four being mostly unused.<br clear="none"> <a shape="rect" href="https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F" rel="nofollow" target="_blank">https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F</a><br clear="none"> <a shape="rect" href="https://metrics.torproject.org/userstats-bridge-transport.html?start=2021-11-10&end=2022-02-08&transport=snowflake" rel="nofollow" target="_blank">https://metrics.torproject.org/userstats-bridge-transport.html?start=2021-11-10&end=2022-02-08&transport=snowflake</a><br clear="none">Since 2022-02-03, it appears that Metrics is showing only one of the<br clear="none">four running instances per day. Because all four instances are about<br clear="none">equally used (as if load balanced, go figure), the values on the graph<br clear="none">are 1/4 what they should be. The reported bandwidth of 5 MB/s is<br clear="none">actually 20 MB/s, and the 2500 clients are actually 10000. All the<br clear="none">necessary data are present in Collector, it's just a question of data<br clear="none">processing. I opened an issue for the Metrics graphs, where you can also<br clear="none">see some manually made graphs that are closer to the true values.<br clear="none"> <a shape="rect" href="https://bugs.torproject.org/tpo/network-health/metrics/onionoo/40022" rel="nofollow" target="_blank">https://bugs.torproject.org/tpo/network-health/metrics/onionoo/40022</a><br clear="none"><br clear="none">I started a thread on tor-dev about the issues of onion key rotation and<br clear="none">ExtORPort authentication.<br clear="none"> <a shape="rect" href="https://lists.torproject.org/pipermail/tor-dev/2022-February/thread.html" rel="nofollow" target="_blank">https://lists.torproject.org/pipermail/tor-dev/2022-February/thread.html</a><div id="ydp166507d0yiv7032496842ydpdd05d81eyqtfd01029" class="ydp166507d0yiv7032496842ydpdd05d81eyqt9639941144"><br clear="none">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none"><a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none"><a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none"></div></div>
</div>
</div></div></div></div></div><div class="ydp166507d0yqt7447743296" id="ydp166507d0yqt84004">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none"><a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none"><a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none"></div></div>
</div>
</div></div></body></html>