- tor-relays - lists.torproject.org

Relay in AT marked as DE in metrics
by Carlo P. 04 Feb '24

04 Feb '24

Hello, I have a relay on 152.53.17.183 / 2a0a:4cc0:1:1333::beef which is listed as "German" in metrics.torproject.org, but actually it is in Austria (see e.g. whatismyip.com) Is this the right place to request a fix ? Thanks, C. -- Sent with https://mailfence.com Secure and private email

3 3

Relay first seen reset on Tor metrics
by Zachary 30 Jan '24

30 Jan '24

The "first seen" date on my relay A00E3AAF5A24DC69740FA7A3A1C4A0ECB7972722 Got reset today while I was at work. It's not a problem and I don't particularly care, but is there anything that would cause this? IP hasn't changed, Tor version hasn't changed, etc. Thanks, Zachary

2 1

Setting up HTML page for exit relay
by templeos＠skiff.com 29 Jan '24

29 Jan '24

If I want to serve an HTML page for my exit node do I need Apache2/nginx or can I just modify my torrc?

3 2

tor relayS! stuck at 100% bootstrapped - not kickstarting 8B6A6D02A80A7CBB1ED0630150D8D9F9F7D471AF
by eff_03675549＠posteo.se 29 Jan '24

29 Jan '24

Hi. I am trying several Singapoor relays stuck at 100% bootstrapped without any coming speed evaluation nor id key attributions, 8B6A6D02A80A7CBB1ED0630150D8D9F9F7D471AF one middle/guard out of 4/5 came out witn keys an shows in relay search still without any speed attribution now over 48 hours, the others (guards, exit) are tusk at 100% bootstrapped. all in singapoor. Your kind evaluation please. an.

1 0

What a mess with the database of 'metrics.torproject.org'!
by Tschador 24 Jan '24

24 Jan '24

Example: Fingerprint: 9D5A7A81BC6194555CE751F75FB196E4A3982CC5 This relay appears to be less than 2 weeks old. Uptime 43 days 13 hours 30 minutes and 17 seconds First Seen 2024-01-10 16:00:00 (14 days 2 hours 32 minutes and 41 seconds) Last Restarted 2023-12-12 05:02:24 When will it be fixed? Regards

1 0

Why is Cloudflare displayed when I do a speed test?
by templeos＠skiff.com 19 Jan '24

19 Jan '24

A blog post I discovered brought up that when they perform a speed test through Tor browser, Cloudflare is quite frequently displayed as the local host. I had the same result. Is there a reason for this, like perhaps the exit relay is proxied through Cloudflare? You can easily replicate this yourself by going to speedtest.net in Tor Browser.

1 0

A new kind of attack?
by Chris Enkidu-6 19 Jan '24

19 Jan '24

I've noticed a new kind of possible attack on some of my relays, as early as Dec.23 which causes huge spikes of outbound traffic that eventually maxes out RAM and crashes Tor. The newest one today lasted for 5 hours switching between two of the three relays on the same IP. During the attack, Tor becomes so busy processing the traffic that it becomes unresponsive to new connections for minutes at a time and effectively becomes a zombie exclusively processing the attacker's traffic until it eventually crashes and restarts. The interesting part is that when Tor restarts, it doesn't start from scratch building new circuits but it starts right from where it left out and keeps processing the previous connections. I have tried shutting down Tor for over 5 minutes and within one minute of restart, The RAM maxes out and the outbound traffic reaches the previous heights. This has been happening, not to all relays but to a select group of relays at a time and unless you're monitoring your Tor port from outside, you may not notice it's unresponsive. Another way to see if it's happening to you too is to check your monthly history on the metrics page and look for spikes of written bytes or sudden decrease of read bytes where you see a big gap between the two. I have included charts and excerpts from the log in my post in Tor forum at below link: https://forum.torproject.org/t/new-kind-of-attack/11122 I'd appreciate your insights and comments. Thank you.

6 5

Re: [tor-relays] Relay in Japan being marked as a US relay?
by 0tpcqovw＠duck.com 18 Jan '24

18 Jan '24

https://www.infobyip.com/ip-198.13.48.219.html Shows Japan! Malcolm On Thu, Jan 18, 2024 at 4:00 PM NodNet < tor_at_nodnetwork.org_0tpcqovw(a)duck.com> wrote: > I think tor and Tor Project use IPFire's DB for GeoIP lookups, and > 198.13.48.219 shows the following: > > NETWORK: 198.13.48.0/20 > AUTONOMOUS SYSTEM: AS20473 - AS-CHOOPA > COUNTRY: United States of America > > https://www.ipfire.org/projects/location/lookup/198.13.48.219 > > On 1/18/2024 11:22 AM, Jag Talon wrote: > > Hello, > > > > I have a relay in Japan with the IP of 198.13.48.219, but it's being > > marked as being in the US. I've tried using different websites like > > www.iplocation.net, iplocation.io, and www.wolframalpha.com and > > they're all telling me that the IP is in Japan. > > > > I'm wondering if perhaps there's an issue with the GeoIP lookup? Or > > perhaps an outdated database? > > > > Thanks! > > > > > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >

2 1

Relay in Japan being marked as a US relay?
by Jag Talon 18 Jan '24

18 Jan '24

Hello, I have a relay in Japan with the IP of 198.13.48.219, but it's being marked as being in the US. I've tried using different websites like www.iplocation.net, iplocation.io, and www.wolframalpha.com and they're all telling me that the IP is in Japan. I'm wondering if perhaps there's an issue with the GeoIP lookup? Or perhaps an outdated database? Thanks! -- Jag Talon Designer for the Tor Project

8 10

PSA: Tor 0.4.7 reaches end of life (EOL) on 2024-01-31
by Georg Koppen 17 Jan '24

17 Jan '24

Hello! In case it affects you as you are still running your relay or bridge on Tor 0.4.7.x: the 0.4.7 series is going EOL on *2024-01-31* (roughly in 2 weeks from now). That's currently still 1346 relays, which means roughly 15% of the advertised bandwidth of the network (and 964 bridges, which means roughly 45% of the advertised bridges bandwidth). Please make sure you have upgraded to the 0.4.8.x series by then. Supported releases in general can be found on the network team wiki.[1] Thanks, Georg [1] https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorRele…

1 0