From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.210.80] (unknown [182.2.41.36]) by gnuweeb.org (Postfix) with ESMTPSA id 940CF80866; Wed, 31 Aug 2022 07:48:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1661932134; bh=9F/IS2ZBEmLkM6RC1gnyjtlGpayUf46uFgBcjBm1nS8=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=QvS4bFvEWBzOZLUqpJN43pir14Gz10v62ROOPkomibuJazWR3y+yN3Vd8YDx8RwG2 zpvkt4FEwPLuzHA5X+gqGBGF4BV7UXtmEY/93CNtCEODmFTjDmQue91l442TP9Q9W4 89zowcN6Ie9f7MKShADh2/a/sdw6Xq53ngeHZzOo3lKTNEspSVIW9Cj3OJUJ2cronQ RhKHPu1yOwOmpgwxJ0JPu3pSh8Xs8f0QX0UCeXKFrtk02upIP0q5ovM+skhr3gMN77 MZkRXhykWaSYT8LAmUbg7t07hStCnRZ85hgTMnXNXxW9SvivzJQLPqiVJ5nv9rCkWm NrC0mnoCbRCzw== Message-ID: <8139f3ff-0f6e-b363-dda8-f5a8f4265732@gnuweeb.org> Date: Wed, 31 Aug 2022 14:48:49 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-US To: Georg Koppen Cc: bad-relays , GNU/Weeb Mailing List , Louvian Lyndal References: <291c272c-f3c6-6479-1b00-bf8c57ec9cf6@gnuweeb.org> <6827c274-5a85-aa8f-b41f-ccf520d7aad6@torproject.org> <1f42f7e1-8691-5b15-36c3-a7470294867c@gnuweeb.org> <903389a3-1c36-4bf3-cb30-7c12cb9b98ed@gnuweeb.org> <2aba6c4e-04c9-3e66-1293-583e68d8307d@torproject.org> <0238b664-2822-7db1-da0e-3f4424737b51@torproject.org> <6e0c8443-8e10-2b2c-6401-39d72f8d4455@gnuweeb.org> <50a99217-06d5-6404-9e5a-070dd1777d14@torproject.org> From: Ammar Faizi Subject: Re: Your TeaInside relay is failing to relay exit traffic In-Reply-To: <50a99217-06d5-6404-9e5a-070dd1777d14@torproject.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: On 8/31/22 2:25 PM, Georg Koppen wrote: > Ammar Faizi: >> On 8/31/22 1:37 PM, Georg Koppen wrote: >>> Ammar Faizi: >>>> On 8/30/22 6:14 PM, Ammar Faizi wrote: >>>> My exit node is now working properly. I also have just re-activated >>>> the IPv6 support on it. My Tor browser is now working fine and I can >>>> confirm the exit IP matches with my exit node server. >>>> >>>> While I don't actually know the reason behind this issue, it's all >>>> fixed now. I also learned more about Tor network. >>> >>> Great, what did you change? >> >> Too many things to tell. I adjusted several configurations in torrc. >> Not sure what the issue was. But now my exit node is marked as BadExit >> and can't relay exit traffic again (after previously several hour >> working well). >> >> Could you elaborate on what is going wrong? How to fix BadExit? > > The problem was that I still saw the same issues yesterday when testing > and got the directory authorities to badexit your node as I did not know > how long this problem persisted. I can redo my test later today and see > how that goes. I see, I understand, thanks! > 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. - 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. -- Ammar Faizi