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 with tor 0.2.6.2-alpha due to some bootstrap speed improvements, although with larger networks you may need to use --delay to increase the bootstrap time.
I suggest you start with --flavour basic-min, and move through the sizes to --flavour basic-100 (my machine can barely run basic-100).
You can also manually modify the amount of random data sent while verifying connectivity (look for "Octets" in chutney's TorNet.py). It would be nice if this amount was configurable (patches gladly accepted).
It would also be nice if these connections were done in parallel, but I don't think that's the case (clarification or patches gladly accepted).
teor
Date: Sun, 11 Jan 2015 14:18:01 +0100
From: webmaster <webmaster@xxxxxxxxxxxxxxxxxxxx>
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 of a high traffic load on my relay
to perhaps adjust my server settings (number of open file descriptors,
...).
Am 11.01.2015 um 13:05 schrieb Julien ROBIN:
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 wgets simultaneously)
Of course, doing that you consume some useful bandwidth for users (but if it's quick, after all you're a Tor user like another!)
And it's not totally the same that relaying data as server, since it's using the client part of the tor process (but starting from here, I cannot help you anymore since I don't know what is written in the code ;)
So if anybody have another better idea
Something that would generate a full customized circuit for example, or reduce the amount of used hop for the test.
It already exists "EntryNodes" and "ExitNodes" commands for your torrc file, but no server can be used as EntryNode if it's not Guard already, and I'm not sure that some "MiddleNodes" command exists.
Last things, you can also make you machine's CPU working hard on a lot of threads simultaneously, and watch if Tor is suffering or not (like "too many circuit creation request!" in the log).
Or make some tests with Iperf for high bandwidth load in parallel ("iperf -s" on a fast machine, "ipers -c Ip -t TimeInSeconds -p port -P ParallelsTcpConnexions" on the other machine - this one will send data (chains of 1234567890123...) to the server)
Good luck ! By curiosity, I'm interested also, but I would understand if this kind of easiness in creating bandwidth statistics and degraded path (for analysis, for example) is not really sought by developers.
Best regards,
Julien ROBIN
----- Mail original -----
De: "webmaster" <webmaster@xxxxxxxxxxxxxxxxxxxx>
?: tor-relays@xxxxxxxxxxxxxxxxxxxx
Envoy?: Dimanche 11 Janvier 2015 11:59:12
Objet: [tor-relays] Simulate High Tor Load
Hey Folks,
is there a common procedure for testing a tor server for a high load?
Thanks in advance
|