GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Georg Koppen <[email protected]>
Cc: bad-relays <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Louvian Lyndal <[email protected]>
Subject: Re: Your TeaInside relay is failing to relay exit traffic
Date: Thu, 25 Aug 2022 14:18:24 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


[-- Attachment #1.1.1: Type: text/plain, Size: 769 bytes --]

On 8/25/22 1:58 PM, Georg Koppen wrote:
> Hello!
> 
> Your TeaInside relay[1] seems to fail relaying exit traffic
> according to our measurements. We ran some tests and it was not possible
> in 5/5 cases to reach e.g. https://torproject.org. Could you please look
> into that and resolve the issue on your end?
> 
> Please let us know if you have further questions and when the problem is
> resolved on your side.
> 
> Thanks for running relays!
> Georg
> 
> [1] https://metrics.torproject.org/rs.html#details/F241330F16AF6BD90226CC9130DA8E20B58AAC3B

Hi Georg,

Thanks for reporting this issue.

I will take a look into it. But before that, I have a question. How do I
test my exit relay to see whether it's working properly?

-- 
Ammar Faizi

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1795 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-08-25  7:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  6:58 Your TeaInside relay is failing to relay exit traffic Georg Koppen
2022-08-25  7:18 ` Ammar Faizi [this message]
2022-08-25  7:33   ` Louvian Lyndal
2022-08-25  7:48     ` Ammar Faizi
2022-08-25  9:27   ` Georg Koppen
2022-08-25 10:13     ` Ammar Faizi
2022-08-30  5:57       ` Ammar Faizi
2022-08-30 11:02         ` Georg Koppen
2022-08-30 11:14           ` Ammar Faizi
2022-08-30 14:12             ` Ammar Faizi
2022-08-31  0:13               ` Ammar Faizi
2022-08-31  6:37               ` Georg Koppen
2022-08-31  6:45                 ` Ammar Faizi
2022-08-31  7:25                   ` Georg Koppen
2022-08-31  7:48                     ` Ammar Faizi
2022-08-31 12:49                       ` Ammar Faizi
2022-08-31 13:25                         ` Georg Koppen
2022-08-31 13:37                       ` Georg Koppen
2022-08-31 14:02                         ` Ammar Faizi
2022-08-31 14:07                           ` Ammar Faizi
2022-08-31 14:32                             ` Louvian Lyndal
2022-08-31 14:46                               ` Georg Koppen
2022-08-31 14:58                                 ` Ammar Faizi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox