<html><head></head><body><div class="ydp8b9c3f73yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>Georg,</div><div><br></div><div>Yes! That is precisely it!</div><div><br></div><div>Please know that the change appears to be working with my loadbalanced Tor Relay deployment as well.</div><div><br></div><div>Are there any "Issues" submitted for a similar change to Concensus Weight and Relay Probability to Tor Metrics on Onionoo? It appears these values are still only being reported for a Single Tor Node.</div><div><br></div><div>A BIG Thank You to the Tor Metrics Team for the Issue-40022 implementation.</div><div><br></div><div>Respectfully,</div><div><br></div><div><br></div><div>Gary</div><div class="ydp8b9c3f73signature">—<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="ydp8b9c3f73yahoo_quoted_6531346340" class="ydp8b9c3f73yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, March 3, 2022, 1:28:12 PM MST, Georg Koppen <gk@torproject.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Gary C. New via tor-relays:<br clear="none">> David,<br clear="none">> Has Tor Metrics implemented your RFC related to Written Bytes per Second and Read Bytes per Second on Onionoo?<br clear="none"><br clear="none">That's probably<br clear="none"><br clear="none"><a shape="rect" href="https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40022" rel="nofollow" target="_blank">https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40022</a><br clear="none"><br clear="none">, no?<br clear="none"><br clear="none">Georg<br clear="none"><br clear="none">> As of the 27th of February, 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?<br clear="none">> 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?<br clear="none">> Thank you for your response.<br clear="none">> Respectfully,<br clear="none">> <br clear="none">> Gary—<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)<br clear="none">> <br clear="none">> On Tuesday, February 8, 2022, 11:49:47 PM MST, Gary C. New via tor-relays <<a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a>> wrote:<br clear="none">> <br clear="none">> David,<br clear="none">> Excellent Documentation and References!<br clear="none">> I hope the proposed RFC's (auth, key, and metrics) for loadbalanced Tor topologies are seriously considered and implemented by Tor Core and Tor Metrics.<br clear="none">> Great Work!<br clear="none">> Respectfully,<br clear="none">> <br clear="none">> Gary—<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)<br clear="none">> <br clear="none">> On Tuesday, February 8, 2022, 10:02:53 AM MST, David Fifield <<a shape="rect" href="mailto:david@bamsoftware.com" rel="nofollow" target="_blank">david@bamsoftware.com</a>> wrote:<br clear="none">> <br clear="none">> 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><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><div class="ydp8b9c3f73yqt5583099642" id="ydp8b9c3f73yqtfd65552"><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">> <br clear="none">> <br clear="none">> <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"><br clear="none"></div></div><div class="ydp8b9c3f73yqt5583099642" id="ydp8b9c3f73yqtfd19161">_______________________________________________<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>