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: Wed, 31 Aug 2022 21:07:30 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

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:
>>>> In the meantime: could you elaborate on why you have the
>>>> DNSPort/TransPort setup and those many SocksPorts configured? That's
>>>> pretty unusual for a plan exit node setup and not needed.
>>>
>>> I run a VPN service that uses the transparent proxy and DNSPort in the
>>> same server with the exit node. I also use the SOCKSPort to run my
>>> scraper app.
>>>
>>> Side note: The amount of the traffic from the VPN and SOCKS is fairly
>>> small, it shouldn't affect my exit node.
>>>
>>> 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.

>> One thing that makes me wonder is that we encounter more and more websites
>> that deploy either total bans on Tor users or annoying CAPTCHAs etc. because
>> of folks massively scraping their contents and because all simpler scraping
>> solutions are already blocked. Are you aware of that issue?
>> (FWIW: that is having a big impact on Tor's overall usability).
> 
> Yes, I am aware of this issue. I have been bitten by annoying CAPTCHAs, block,
> etc. when using Tor network. So I understand.
> 
>>>    - TeaVPN2 service (TransPort and DNSPort).
>>>
>>>      I am writing a VPN software (Linux). It uses the transparent
>>>      proxy and DNS port only for accessing "*.onion" host. Only
>>>      3 people using it so far, rarely used too.
>>>
>>> Is it fine doing that?
>>>
>>> I can deploy a dedicated Tor instance for my VPN and scraper app if
>>> it is really needed.
>>
>> Well, "needed" might be to strong here but it is certainly encouraged to
>> just relay Tor exit traffic with your server as whatever else you are
>> running and doing on that box might affect that exit relay which in turn
>> might impact (other) Tor users.
> 
> Understand, thanks!
> 

-- 
Ammar Faizi

  reply	other threads:[~2022-08-31 14:07 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 [this message]
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