Scott Bennett:
> Georg Koppen wrote:
>
>> Some of you might remember the speed test Rob had been running during
>> August 2019 to investigate the accuracy of the advertised bandwidth a
>> relay is reporting in its server descriptor.[1] Back then this involved,
>> for each relay, downloading sever
Pluggable Transport process terminated with status code 256
ServerTransportPlugin obfs4 exec /user/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:
Monica
--
This email has been checked for viruses by AVG.
https://www.avg.com
___
Date: Tue, 11 May 2021 18:49:46 -0500
From: Kathi
To: tor-relays@lists.torproject.org
Subject: [tor-relays] Bridge Transport Issue
Message-ID: <6579c990-2adc-e9e8-d022-d3ad93cdd...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
?Pluggable Transport process terminated with sta
On Wednesday, May 12th, 2021 at 01:49, Kathi wrote:
> Pluggable Transport process terminated with status code 256
> ServerTransportPlugin obfs4 exec /user/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:
>
> Monica
Maybe add: ExtORPort auto
and check if: BridgeRelay 1
Mayb
> Okay, I read that, but I do not see where you offer any method to
> account for other traffic that the relay being tested may be dealing with
> at the time you are testing it. IOW, your testing procedure would be fine
> if only the tor network, or at least each relay while i
