After suffering the loss of maatuska's bwauth several months ago, we have re-provisioned it thanks to the gracious help from https://coldhak.ca/
It has completed an initial scan of the network[0] and is reporting its data here: http://198.51.75.50/bwauth/bwscan.V3BandwidthsFile
This week I intend to flesh out the remaining aspects of the bwauth (debug logging, alerting to detect downtime, get a proper domain name, ssl cert, etc) as well as do some sanity checking on its output. If all goes well, I'll submit it to maatuska for inclusion at the end of the week.
But I wanted to announce it here, both to give an update, and let the community take a look at its output and see if anything looks fishy. The bwauths themselves tend to disagree, partly because of the eb and flow of network speeds and partly because they are designed to (they all measure from different network vantage points) - but they ideally are in some sort of rough agreement.
-tom
[0] "Measured 99.7% of all tor nodes (99.6% of previous consensus bw)."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 08/14/2017 11:22 PM, Tom Ritter wrote:
But I wanted to announce it here, both to give an update, and let the community take a look at its output and see if anything looks fishy.
Since few hours the BW is dropped or my exit relay from about 90,000 to 20 accordingly to [1]. A quick check showed that few more relays are affected too.
[1] https://consensus-health.torproject.org/consensus-health-2017-08-16-16-00.ht...
- -- Toralf PGP C4EACDDE 0076E94E
That is because gabelmoo's bwauth dropped off. Now there are only 3 bwauths in the system, and your relay was not measured by one of them (faravahar). With only 2 measurements, you get kicked down to the default I believe.
The good news is that my bwauth measured you at 75600, which is a bit below the other two measurements, but in line with them. So once maatuska starts voting on this data you'll be popped back up.
Please bear with us while we get this sorted out! =)
-tom
On 16 August 2017 at 14:36, Toralf Förster toralf.foerster@gmx.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 08/14/2017 11:22 PM, Tom Ritter wrote:
But I wanted to announce it here, both to give an update, and let the community take a look at its output and see if anything looks fishy.
Since few hours the BW is dropped or my exit relay from about 90,000 to 20 accordingly to [1]. A quick check showed that few more relays are affected too.
[1] https://consensus-health.torproject.org/consensus-health-2017-08-16-16-00.ht...
Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE-----
iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWZSeohccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTjVtAP9jnze4wzptyJvHJmEZEoXBFdik 4alXQ+93w7ITJJLmVgD/dtitebS/ASbD2e41065+z9iZALCd19qkqotRldo04J8= =V6zw -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 08/16/2017 10:06 PM, Tom Ritter wrote:
That is because gabelmoo's bwauth dropped off. Now there are only 3 bwauths in the system, and your relay was not measured by one of them (faravahar). With only 2 measurements, you get kicked down to the default I believe.
The good news is that my bwauth measured you at 75600, which is a bit below the other two measurements, but in line with them. So once maatuska starts voting on this data you'll be popped back up.
Please bear with us while we get this sorted out! =)
Ah, thx for the info. I was a little bit unsettled /c I changed my iptables ruleset around the same time where BW dropped down.
- -- Toralf PGP C4EACDDE 0076E94E
Tom Ritter tom@ritter.vg wrote Wed, 16 Aug 2017 15:06:55 -0500:
The good news is that my bwauth measured you at 75600, which is a bit below the other two measurements, but in line with them. So once maatuska starts voting on this data you'll be popped back up.
maatuska is now voting on bandwidth measurement data from Tom's bwauth.
tor-relays@lists.torproject.org