[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Re: Netscan Hetzner

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] Re: Netscan Hetzner
From: Marco Moock via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 29 Dec 2025 12:16:29 +0100
In-reply-to: <7D5F8587-C146-4F89-A659-A3FCAE763DD9@tobiassachs.de>
List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
References: <7vchsr2XZk4eSmAhiixp7WxaHFgDyUDtO-Yf6TnYyoyFqO_SNNirpXXplMGTTcmSJx7zx4GzniRJt34iyM2Km1AEtJjKYobCcxwxgUZYXtQ=@protonmail.com> <7D5F8587-C146-4F89-A659-A3FCAE763DD9@tobiassachs.de>
Reply-to: Marco Moock <mm@xxxxxxxxxx>

On 29.12.2025 03:24 Tobias Sachs via tor-relays wrote:

> I just blocked the ranges to prevent the relay from being shut down.
> 
> ufw deny out to 64.65.0.0/22
> ufw deny out to 64.65.62.0/23
> ufw deny out to 96.9.98.0/24
> ufw deny out to 216.181.20.0/24

I can ping 64.65.0.0 via the publicly available RIPE/GLOBALPLING probes.

Are you sure this is a persistent routing issue?
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx

References:
- [tor-relays] Netscan Hetzner
  - From: Diyar Ciftci via tor-relays
- [tor-relays] Re: Netscan Hetzner
  - From: Tobias Sachs via tor-relays

Prev by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Previous by thread: [tor-relays] Re: Netscan Hetzner
Next by thread: [tor-relays] Manual calculation of the bridge-moji
Index(es):
- Author
- Thread