public inbox for [email protected]
 help / color / mirror / Atom feed
From: Georg Koppen <[email protected]>
To: Ammar Faizi <[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 09:27:23 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


[-- Attachment #1.1: Type: text/plain, Size: 1611 bytes --]

Ammar Faizi:
> 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?

There are different ways. One thing we do is to build circuits with the 
respective nodes to test as exits and then we try to connect to 
different websites and check whether there are any failures. In your 
case it seems connections are timing out.

Another way, which you could try is using Tor Browser with your node as 
exit node. For that, after you have downloaded Tor Browser and extracted 
it, add to your torrc file (in 
tor-browser_en-US/Browser/TorBrowser/Data/Tor):

ExitNodes F241330F16AF6BD90226CC9130DA8E20B58AAC3B

The start Tor Browser and try to surf to some websites like popular news 
sites etc. Those requests are frequently timing out or take super long 
to load resulting caused by lots of circuit churn (as the circuit fails 
due to timeouts).

Hope this helps,
Georg



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

  parent reply	other threads:[~2022-08-25  9:27 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
2022-08-25  7:33   ` Louvian Lyndal
2022-08-25  7:48     ` Ammar Faizi
2022-08-25  9:27   ` Georg Koppen [this message]
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 \
    --in-reply-to=6827c274-5a85-aa8f-b41f-ccf520d7aad6@torproject.org \
    [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