| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
| |
Now works via --tor and --tor-gencert.
Overridden by the build directory set via --tor-path and $TOR_DIR.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Return immediately on success.
Only return failure after 60 seconds with no successes.
This makes networks that bootstrap quickly verify much faster,
and networks that bootstrap slowly are much more reliable.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Rewrite test-network.sh so out-of-tree and $PATH binaries work
Add a dry run mode to test-network.sh
We fixed #15937, update a comment
|
| |
|
|
| |
This script comes from Tor git 9932544 on 2016-07-13.
|
| |
|
|
|
| |
Uses the text from the #18826 commit message, with modifications.
Adds a note about IPv6, which is a work in progress.
|
| | |
|
| | |
|
| |
|
|
|
| |
You can replace the standard chutney tests with custom scripts.
But you probably shouldn't.
|
| |
|
|
|
|
| |
Based on a patch from chobe.
Closes ticket 9087.
|
| |
|
|
|
|
| |
It's controlled via the CHUTNEY_LISTEN_ADDRESS environment variable
(default: localhost). Setting it to some interface's IP address
allows us to make the simulated Tor network available on the network.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It is controlled with the CHUTNEY_DATA_DIR environment variable, but
defaults to the 'net' sub-directory of the Chutney source tree.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow chutney exits to exit to all private addresses.
Tidy up exit policies, so each part of the policy is clearly identified.
Document alternatives to work around #11264, the microdescriptor
2x /8 requirement for exits.
Prepare for resolving #15353 by making sure the exit policies *should*
work when localhost is the only available IP. This still requires further
investigation.
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| | |
When chutney verify fails, tell the user how to activate debug mode
by editing the source code.
Eventually, we'll make debug mode an argument, see #15418.
|
| | |
| |
| |
| |
| | |
Otherwise it may make this step of the configuration fail, e.g. if a
hidden service is configured system wise.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The `%` operator needs to go inside the call to the `print()` function.
Otherwise, the format string operation is being done on the return value of
`print()`, which is `None`.
* FIXES #18341: https://bugs.torproject.org/18341.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes Chutney on systems which have python2 in their PATH but not
python.
Portability of the script has improved by avoiding `command` and instead
walking through PATH. This code is based on the program detection in
Autoconf.
Usability has improved by displaying a message when no compatible Python
version has been found which advises the user to check their Python
installation and PATH. When a compatible Python version has been found,
the script displays the Python version before initializing Chutney.
Fixes ticket 17631.
|
| | |
| |
| |
| |
| | |
When we fail to send bytes, sleep for 1 second before retrying.
This avoids trying a few thousand times a second.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This only seems to happen when all external network interfaces are down.
But Tor should still work using 127.0.0.1.
This requires further investigation.
Investigatory changes for #15353.
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If $PYTHON isn't set, use "command" to check for python2, then python.
(python3 check is disabled due to #16904 - chutney doesn't work with
python3.)
If neither of the "command" checks work, assume a strange shell or "command",
and fall back to python2.
Fixes default install of chutney on OS X, which has neither $PYTHON set,
nor python2; but does have python, which happens to be version 2.
Resolves #16902.
|
| |/ /
| |
| |
| | |
This network allows non-IPv6 systems to test almost all tor functionality.
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The following environmental variables affect chutney verify:
CHUTNEY_DATA_BYTES=n sends n bytes per test connection (10 KBytes)
CHUTNEY_CONNECTIONS=n makes n test connections per client (1)
CHUTNEY_HS_MULTI_CLIENT=1 makes each client connect to each HS (0)
When enough data is transmitted, chutney verify reports:
Single Stream Bandwidth: the speed of the slowest stream, end-to-end
Overall tor Bandwidth: the sum of the bandwidth across each tor instance
This approximates the CPU-bound tor performance on the current machine,
assuming everything is multithreaded and network performance is infinite.
These new features are all documented in the README.
|
| | | |
| | |
| | |
| | | |
Each network has exits flagged with exit=1
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Also perform minor clean-up in some files.
This is required for the performance testing changes.
|
| |/ /
| |
| |
| |
| |
| | |
Refactor existing templates to avoid duplication.
This makes flagging each exit for performance testing much easier.
|
| |/
|
|
| |
Resolves bug 16310 - chutney thinks tor fails to launch under high load.
|
| |
|
|
|
| |
This means setting CHUTNEY_PATH to the git checkout just works from
inside Tor.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chutney verify now verifies bridge clients and hidden services.
Bridge clients are verified just like clients, by using an exit to
connect to the TrafficTester's listening port.
Hidden services are verified by using an arbitrary client
(the first one in the list) to connect to the hidden service.
The hidden service is configured to redirect data to the
TrafficTester's listening host:port.
This works almost exactly like the standard client / bridge client tests.
The only difference is that the client connects via a hidden service port
pre-configured with a specific redirect, rather than via an exit which
could handle arbitrary hosts and ports.
Also review the number of relays/exits/authorities required for the 25%
guard changes. For 2 guards, 8 relays are required in total,
including authorities and exits.
|
| |
|
|
| |
Test bridge clients using chutney verify, the same way we test clients.
|
| |
|
|
|
|
|
|
|
| |
Add a new env hs (boolean) that is set to 1 for hidden services.
Add a new env hs_directory (string) that is set to the name of the hidden
service directory ('hidden_service' by default).
When hs is 1, create hs_directory with mode 0700 (448 decimal).
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Speed up the tor bootstrap by modifying both tor and chutney.
Comprehensive bootstrap: (30s)
Reduce the consensus interval to 10 seconds
Depends on corresponding tor changes
Don't require any bandwith for an exit flag
Depends on corresponding tor changes
Fast Bootstrap: (10s)
Assume that everything is reachable and an exit
Start building paths once the minimum number of descriptors are available
Reduce consensus validity to 2 intervals
Also make other minor config fixes
Resolves bug 13823. Tests resolution of (tor) bug 13718 and children.
|
| | | |
|
| | | |
|