Hi
most of my relays are no longer listed on Torstatus* and Consensus**.
But they perform like they should.
out $E388F7BD196F5195AEF114552585152EA6942329
out $2691AE47D3E1D5702520F2792951927C9FE82C67
out $8d1a618c523a8cc761b7253e96c6d19285c47029
out $05d54acea361a57b16cd461340bd3
Hey Folks,
is there a common procedure for testing a tor server for a high load?
Thanks in advance
--
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.17 (MingW32)
mQENBFHMmT8BCAC0smvU7Bq1ABxAhvBRn7d4ekkk95aCE4TTQo4wy1z/rGLhQfdt
dhiD+Vy61vGrsdK3ei5sW6rBvX2m8+YmBi+8AAgSiZmS0JM3Zz3cmTi5
Hi,
If you are on a dedicated high Bandwidth server you can maybe use your relay as
client, an idea could be to open a lot of "wget" commands.
sudo apt-get install torsocks
usewithtor wget URL
But it's not guaranteed that the selected circuits will be super-fast (first
reason to open lot of wg
Hi Julien,
thats exactly the setup I'm actually using. I use my relay as a client.
>From my point of view it seems that the relay is used as a entry point
(without guard flag) in this constellation (correct me if I'm wrong).
Torsocks could solve my problem.
My goal is to examine the influence o
Hi Felix,
Same here, atlas and globe went down for me at that period.
On 11 January 2015 at 11:40, Felix wrote:
> Hi
>
> most of my relays are no longer listed on Torstatus* and Consensus**.
> But they perform like they should.
>
> out $E388F7BD196F5195AEF114552585152EA6942329
> out $26
What an interesting coincidence, tor-specific load is down to about
1/3 of its' normal which is in the 20mb/s range usually.
I was worried my experimentation got me dinged as a badexit but that's
not the case, and otther people are seeing odd things...
On Sun, Jan 11, 2015 at 7:40 AM, ZEROF wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Having discussed this with my partner earlier today, I am curious as
to what knowledge the community might have on overclocking a CPU or
using other speciality hardware to create an ultra fast Tor relay. I
am aware of what IPredator have done but I f
Hi,
chutney can be used to setup a large test tor network running solely on a
single machine, with no outside network access required.
The tor/src/test/test-network.sh script will configure an entire test tor
network and verify connectivity from each client through the network.
This works best
Hi List,
I'm seeing these messages in one of my relays. Pretty often, too.
eventdns: Address mismatch on received DNS packet. Apparent
source was :
I've searched this and found references[1] to a faulty resolver of
some type and torservers.net ignores the message[2]. I use my ISPs
resolvers
On Sat, Jan 10, 2015 at 10:58 PM, Richard Johnson wrote:
> It is especially a good idea to have your own local DNS resolver if you run
> Tor exits at an institution that's required to otherwise log DNS queries.
>
> Tor needs a separate (and non-logging) DNS resolution system to prevent the
> insti
On Fri, Jan 9, 2015 at 10:26 PM, Drake Wilson wrote:
> eric gisse wrote:
>> Plus the logic starts to get warped when you wonder "So do you BadExit
>> every node that runs on an ISP that caches traffic?"
>>
>> What about ISP's (and openDNS) that NXDOMAIN trap to insert advertising?
>
> These, I thi
> Date: Mon, 12 Jan 2015 01:04:58 -0500
> From: grarpamp
> To: tor-relays@lists.torproject.org
>
>>> On Fri, Jan 9, 2015 at 10:26 PM, Drake Wilson wrote:
>>> eric gisse wrote:
>>> Plus the logic starts to get warped when you wonder "So do you BadExit
>>> every node that runs on an ISP that cach
12 matches
Mail list logo
