>
> There are two ways this can happen:
>
> Someone set up a tor relay on the "client", and your relay connected
> to it.
>
> Someone is using the hidden service rendezvous protocol to ask non-exit
> relays to scan non-tor IP addresses. Specifying a remote address is a
> feature of the protocol. W
> On 22 Sep 2017, at 08:49, relay 000 wrote:
>
> FYI, I got this email for a non-exit relay - please share if you get them as
> well:
>
> ...
>
> You have a system on your network that is actively scanning and/or attacking
> external sites on the Internet. This can come from many sources and
> On 22 Sep 2017, at 08:34, Dylan Issa wrote:
>
> Kurt,
> We are both on OVH but I am on the FRA side, yet my graph seems much more
> steady (and I have more flags than you), despite having slightly less
> bandwidth and slightly less uptime. Is your server being hammered by
> something or in
FYI, I got this email for a non-exit relay - please share if you get them as
well:
To Whom it May Concern,
You have a system on your network that is actively scanning and/or attacking
external sites on the Internet. This can come from many sources and because it
is often difficult to detect
Kurt,
We are both on OVH but I am on the FRA side, yet my graph seems much more
steady (and I have more flags than you), despite having slightly less bandwidth
and slightly less uptime. Is your server being hammered by something or in use
somewhere else?
My similar node:
E08CD0147F9DC5C2383B84D8
E65D300F11E1DB12C534B0146BDAB6972F1A8A48
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
