Re: [tor-relays] Tor bandwidth scanner "longclaw" slow to the US West Coast
Surprisingly, longclaw stopped measuring and the consensus weights shot up. My home ISP, "Wave G" has shitty peering so it didn't shot up as much. But my Psychz dedicated server fortunately did see a solid increase. -Neel On 2020-08-19 16:02, i...@backplanedns.org wrote: Same here https://metrics.torproject.org/rs.html#details/29BBD80A1702C7FDEF6557C492F44E9EBAB2854A _Sent from my T-Mobile 4G LTE device_ -- Original message-- From: Eddie Date: Wed, Aug 19, 2020 6:40 PM To: tor-relays@lists.torproject.org; Cc: Subject:Re: [tor-relays] Tor bandwidth scanner "longclaw" slow to the US West Coast Not sure if my relay is similar, but I've been seeing a slow fall in consensus weight and advertised bandwidth over the past few months even though absolutely nothing has changed at my end. Well, apart from me *increasing* the RelayBandwidth settings. Also before I shut my relay down for a couple of weeks late last year, it had, and maintained guard status for about 6 months. Now it yo-yos in and out of guard on a regular basis. https://metrics.torproject.org/rs.html#details/D195E5CE8AE77BAC91673E6CFB7BD0AF57281646 Cheers. On 8/15/2020 5:41 PM, Neel Chauhan wrote: Hi, Is anyone else hosting West Coast relays having this issue? Is "longclaw" actually measuring bandwidth from Europe? If so, WHY? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] don't publish detailed metrics about your relays
On Thu, Aug 20, 2020 at 8:51 PM nusenu wrote: > > > Don't publish detailed metrics about your relays. > > > Here is a good example what NOT to do with your relays: > > http://51.77.135.89:1/#menu_net_submenu_eno1;theme=slate > http://51.75.144.43:1/#menu_net_submenu_eno1;theme=slate > > The relay guide has detailed guidelines on what granularity is considered > safe. In section "System Health Monitoring" on https://community.torproject.org/relay/setup/post-install/ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Blog: How Malicious Tor Relays are Exploiting Users in 2020 (Part I)
Most of the relays from the first group got added at the exact same time, the second group got added within a few days - tells me someone looking at the OrNetRadar logs isn't doing his job correctly. 2020-08-19 16:27 GMT, nusenu : > niftybunny: >> https://medium.com/@nusenu/how-malicious-tor-relays-are-exploiting-users-in-2020-part-i-1097575c0cac >> >> There are multiple indicators that suggest that the attacker still >> runs >10% of the Tor network exit capacity (as of 2020–08–08) >> >> And on this one: I trust nusenu who told me we still have massiv >> malicious relays. > > as some of you have probably seen already > now a fraction of them got confirmed to run the same attack tools: > https://twitter.com/notdan/status/1295813432843829251 > > Unfortunately this is not the end of it. > > Some of them where directly linked in the blog post above. > > What I'm still wondering about is: What made Tor directory authorities > change their policies and stop removing undeclared relay groups? > > +-+--++-+--+ > | first_seen | nickname | contact| > as_name | fingerprint | > +-+--++-+--+ > | 2020-06-20 01:00:00 | relay23 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 01C05513D12F63AE9E72588E8EAB459028C44689 | > | 2020-06-20 01:00:00 | relay05 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 01DAC406BD545B6EB41D3E12476E70EAE4872407 | > | 2020-06-20 01:00:00 | relay02 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 078A661362B4959F64F8E01DF4646101542E1AD2 | > | 2020-06-20 01:00:00 | relay17 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 11F76D073C30EE2C8849602B90950659E79EB0B0 | > | 2020-06-20 01:00:00 | relay21 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 17B63505746D57A2C3F240C63EA0DDE7B7EB73C8 | > | 2020-06-20 01:00:00 | relay09 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 1970C3CE0F945DA0D16DF5191DC8B0483A421A75 | > | 2020-06-20 01:00:00 | relay30 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 3D20E55FFEB48BB224A510A3740C3FE56036404B | > | 2020-06-20 01:00:00 | relay24 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 40D792754B7B891672288E3705B98C612B002531 | > | 2020-06-20 01:00:00 | relay27 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 4A14A18B4813930E04F49011D56CDA86D0D33E59 | > | 2020-06-20 01:00:00 | relay32 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 4FF250A3701CD24523D1B0A9C1FA760FFE9BF5E6 | > | 2020-06-20 01:00:00 | relay13 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 5C34E92C2F19FA99DB9A680D75C0382E2C91DDE9 | > | 2020-06-20 01:00:00 | relay25 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 5F1381FA3963CAAF712235CA34D6B15FDDF14966 | > | 2020-06-20 01:00:00 | relay22 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 7A6014B07509E75172FCF036CC4E9870260470FF | > | 2020-06-20 01:00:00 | relay07 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 8C28E2857B25C9A92309699416D74AE7AA1A2CCC | > | 2020-06-20 01:00:00 | relay28 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 8DFCD8E4F626AC933A93AC66847F7C5915824171 | > | 2020-06-20 01:00:00 | relay06 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 97F3FDE85A765E009F8F94F03970234C05F82F3B | > | 2020-06-20 01:00:00 | relay29 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | 9D63D167286F731895A2DE06C8BF6D2F549033AD | > | 2020-06-20 01:00:00 | relay08 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | A9EE8826DF8A4E7BDE76CA9740970415516A307E | > | 2020-06-20 01:00:00 | relay03 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | AC7FFC636CD734A0FDC22BF811841AE89743FC4F | > | 2020-06-20 01:00:00 | relay31 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | BEFBEB3E477C77DAA8FB8FA03B6C6ABE71097786 | > | 2020-06-20 01:00:00 | relay11 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | C00CBEE82D153439F4D1D3CDF8406646BCA2DB7E | > | 2020-06-20 01:00:00 | relay26 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | C13BF3056344BDD6F486E1A96C89B76671A17C33 | > | 2020-06-20 01:00:00 | relay10 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | CB78B3066AFFCC9C0DDC9CBBA5642BE162D2CEB9 | > | 2020-06-20 01:00:00 | relay01 | kleinendorstwiebe AT gmail DOT com | > Liteserver Holding B.V. | D7188148CF8CBACDF884C5E6615E82AA46DDB320 | > | 2020-06-20 01:00:00 | relay14 | kleinendorstwiebe AT gmail DOT com | >
Re: [tor-relays] Tor bandwidth scanner "longclaw" slow to the US West Coast
Same herehttps://metrics.torproject.org/rs.html#details/29BBD80A1702C7FDEF6557C492F44E9EBAB2854ASent from my T-Mobile 4G LTE device-- Original message--From: EddieDate: Wed, Aug 19, 2020 6:40 PMTo: tor-relays@lists.torproject.org;Cc: Subject:Re: [tor-relays] Tor bandwidth scanner "longclaw" slow to the US West CoastNot sure if my relay is similar, but I've been seeing a slow fall in consensus weight and advertised bandwidth over the past few months even though absolutely nothing has changed at my end. Well, apart from me *increasing* the RelayBandwidth settings. Also before I shut my relay down for a couple of weeks late last year, it had, and maintained guard status for about 6 months. Now it yo-yos in and out of guard on a regular basis. https://metrics.torproject.org/rs.html#details/D195E5CE8AE77BAC91673E6CFB7BD0AF57281646 Cheers. On 8/15/2020 5:41 PM, Neel Chauhan wrote: > Hi, > > Is anyone else hosting West Coast relays having this issue? Is > "longclaw" actually measuring bandwidth from Europe? If so, WHY? > ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
