GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Georg Koppen <[email protected]>
To: Louvian Lyndal <[email protected]>,
	Ammar Faizi <[email protected]>
Cc: bad-relays <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: Re: Your TeaInside relay is failing to relay exit traffic
Date: Wed, 31 Aug 2022 14:46:28 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAP2ubgJuMydRH-nrx4exi1=BsyOQ_nPhHv2CO+SYzg0+ajRh0g@mail.gmail.com>


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

Louvian Lyndal:
> On 8/31/22 9:07 PM, Ammar Faizi wrote:
>> On 8/31/22 9:02 PM, Ammar Faizi wrote:
>>> On 8/31/22 8:37 PM, Georg Koppen wrote:
>>>> Ammar Faizi:
>>>>> On 8/31/22 2:25 PM, Georg Koppen wrote:
>>>>> Current usage:
>>>>>
>>>>>     - A single small scrapper app (SOCKSPort).
>>>>>
>>>>>       I configure many ports to get many exit IP addresses for
>>>>>       randomizing my identity.
>>>>
>>>> How is that supposed to work given that you only have one exit IP address
>>>> (68.183.184.174)?
>>>
>>> You misunderstood my email.
>>>
>>> I use the SOCKSPort for scraping, this gives me random exit IP. It doesn't
>>> use my exit IP for the scraper's outbound traffic. A simple way to use it
>>> is like this (I expose the ports publicly, you can try it too):
>>>
>>> ```bash
>>>
>>> for i in {64500..64599}; do
>>> curl -4 https://ipecho.net/plain --proxy socks5://68.183.184.174:$i; echo;
>>> done;
>>>
>>> ```
>>>
>>> It's slow, but it works.
>>>
>>>> And what are you actually scraping?
>>>
>>> The current is actively fetching https://lore.kernel.org/io-uring/new.atom
>>> every 30 seconds. I don't see this as a big deal for the Tor network anyway.
>>
>> Just addition to that, previously, Louvian (in the CC) was scraping nhentai.net
>> with those SOCKSPort(s). But it was not a massive traffic.
> 
> I've stopped scraping it for a while, sometimes only running the
> scraper when I want to download a specific gallery number from nh. but
> yes, before it, the scraper was running a bit aggressively for content
> collecting purpose
> 
> I'll stop doing that, I actually enjoy reading nh online more than
> downloading. Our scraping activity (on nh) didn't actually have a
> strong intention, it was just for fun collecting data and happy doing
> code.

I see. Anyway, the DNS issue seems indeed resolved, thanks! I pushed a 
commit to get the badexit flag removed. Once a majority of directory 
authorities has picked it up your relay will be used as an exit again. 
(That might take a couple of hours at least, though)

Thanks for running relays,
Georg


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

  reply	other threads:[~2022-08-31 14:46 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
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 [this message]
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=e2d553ac-898b-3d98-4ada-927d5cb11447@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