Chutney issueshttps://gitlab.torproject.org/tpo/core/chutney/-/issues2020-06-27T13:19:07Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10136Unknown options in torrc file2020-06-27T13:19:07ZTracUnknown options in torrc fileI am new(student) to tor. When I try to run chutney => ./chutney start networks/basic , it is not able to run the tor. When I looked at the torrc file generated and tried running them separately, I got the following warnings:
* Unknown ...I am new(student) to tor. When I try to run chutney => ./chutney start networks/basic , it is not able to run the tor. When I looked at the torrc file generated and tried running them separately, I got the following warnings:
* Unknown option 'TestingClientDownloadSchedule'
* Unknown option 'TestingV3AuthVotingStartOffset'
with this I also got(after commenting above lines from torrc file) :
* TestingV3AuthInitialVoteDelay is way too low
**Trac**:
**Username**: vikassyNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10154Allow a Bridge Authority in Test Networks2020-06-27T13:19:07ZMatthew FinkelAllow a Bridge Authority in Test NetworksCurrently Chutney generates an invalid torrc when the network contains a bridge authority.
```
Nov 13 23:01:36.926 [warn] You cannot set both DirAuthority and Alternate*Authority.
Nov 13 23:01:36.926 [warn] Failed to parse/validate conf...Currently Chutney generates an invalid torrc when the network contains a bridge authority.
```
Nov 13 23:01:36.926 [warn] You cannot set both DirAuthority and Alternate*Authority.
Nov 13 23:01:36.926 [warn] Failed to parse/validate config: Directory authority/fallback line did not parse. See logs for details.
Nov 13 23:01:36.926 [err] Reading config failed--see warnings above.
```Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10764chutney has a non-obvious license2020-06-27T13:19:07ZRoger Dingledinechutney has a non-obvious licenseAt the top of some of the python files in Chutney is this text:
```
# Copyright 2011 Nick Mathewson, Michael Stone
# Copyright 2013 The Tor Project
#
# You may do anything with this work that copyright law would normally
# restrict, so...At the top of some of the python files in Chutney is this text:
```
# Copyright 2011 Nick Mathewson, Michael Stone
# Copyright 2013 The Tor Project
#
# You may do anything with this work that copyright law would normally
# restrict, so long as you retain the above notice(s) and this license
# in all redistributed copies and derived works. There is no warranty.
```
which some folks might recognize as the Tiny license.
But the work as a whole appears to have no license file. So e.g. tools/bootstrap-network.sh would sure look to be non open source software currently.
Can we add a license for the work as a whole?Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10933support for setting binary paths via environment varaibles2020-06-27T13:19:06ZTracsupport for setting binary paths via environment varaiblesMy branch:
https://github.com/houqp/chutney/tree/env_bin
This makes it easier to switch between different builds for testing purpose.
**Trac**:
**Username**: dave2008My branch:
https://github.com/houqp/chutney/tree/env_bin
This makes it easier to switch between different builds for testing purpose.
**Trac**:
**Username**: dave2008Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10934remove stale lock file for crashed Tor2020-06-27T13:19:06ZTracremove stale lock file for crashed TorOn stop command, stale lock files will be checked and removed.
branch:
https://github.com/houqp/chutney/commits/remove_stale_lockfile
**Trac**:
**Username**: dave2008On stop command, stale lock files will be checked and removed.
branch:
https://github.com/houqp/chutney/commits/remove_stale_lockfile
**Trac**:
**Username**: dave2008Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/11340cleaner error ouput for none exist network file2020-06-27T13:19:06ZTraccleaner error ouput for none exist network filebranch:
https://github.com/houqp/chutney/tree/miss_network_error
**Trac**:
**Username**: dave2008branch:
https://github.com/houqp/chutney/tree/miss_network_error
**Trac**:
**Username**: dave2008Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13161[patch] getting chutney working with tor 0.2.6-alpha on OS X2020-06-27T13:19:06Zteor[patch] getting chutney working with tor 0.2.6-alpha on OS XI had several issues getting chutney working on OS X 10.9 with tor 0.2.6.?-alpha. I've attached bug-related patches to this bug. I have created another issue for dependent enhancements. I have also created a bug for my remaining issue wi...I had several issues getting chutney working on OS X 10.9 with tor 0.2.6.?-alpha. I've attached bug-related patches to this bug. I have created another issue for dependent enhancements. I have also created a bug for my remaining issue with the chutney bridges* flavours accessing the global tor network, rather than the chutney network.
tor git d6b2a1709d28c656dadc019fb24145e6ac400771
chutney git 60b2d18d81904e6a71a352dfa8b5cb73f4e04003
= Getting chutney working
== 01-tor-TestingDirAuthVoteExit.patch
The authorities configured by chutney didn't apply the "Exit" flag to the exits in the network until about 35 minutes had passed. This patch creates a test config TestingDirAuthVoteExit which makes authorities mark particular relays as exits, similar to TestingDirAuthVoteGuard. (There may be a better way of getting the authorities to mark exits within seconds rather than half an hour.)
== 02-chutney-authority-force-vote-exit-guard.patch
Use tor-TestingDirAuthVoteExit.patch and TestingDirAuthVoteGuard to make all authorities vote all relays as exits and guards. This ensures that tor's make test-network will work. But it's a sledgehammer approach.
== 03-chutney-explicit-exit.patch
It looks like tor exits need to be explicitly configured to accept all ports on localhost (they won't do it by default).
== 04-chutney-basic-decreased-guards-more-relays.patch
Since the guard percentage has been reduced from 50% to 25% of relays, we need more relays to compensate.
= Fixing chutney issues
== 05-chutney-kill-old-nets-other-flavours.patch
If you change the chutney flavour between runs, tor processes from the previous run sometimes don't get terminated when the next chutney runs. This patch fixes this issue by using pidfiles, and, in the extreme case of kill-zombies.sh, ps and path grepping (which is a hack).
== 06-test-network-wait-25s.patch (optional)
The chutney network seems more reliable if I wait for 25 seconds instead of 18. YMMV
== 07-test-network-echo.patch
The default shell on OS X is bash, which has a builtin echo. When called in "sh" mode, this echo does not accept "-n". This patch uses "/bin/echo -n" instead.
= Debugging tor launched by chutney
== 08-chutney-enable-debugger.patch
This patch sets DisableDebuggerAttachment to 0, because if you're running a test network, you probably don't care about a debugger. (I may be wrong about this.)
== 09-chutney-TorNet-not-RunAsDaemon-comments.patch
I found it hard to debug tor processes launched by chutney when RunAsDaemon was set. So I wrote code that allowed the use of poll() instead of wait() to catch launch failures. This patch includes these changes in the comments - the functionality is the same as the git version of chutney. (There may be a better way of making this an option.)teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13162[patch] Extra flavours for chutney and tor 0.2.6-alpha2020-06-27T13:19:06Zteor[patch] Extra flavours for chutney and tor 0.2.6-alphaAfter I got chutney working on OS X 10.9 with tor 0.2.6.?-alpha (see legacy/trac#13161), I created the attached basic+middle, large, and huge flavours.
tor git d6b2a1709d28c656dadc019fb24145e6ac400771 + legacy/trac#13161
chutney git 60b...After I got chutney working on OS X 10.9 with tor 0.2.6.?-alpha (see legacy/trac#13161), I created the attached basic+middle, large, and huge flavours.
tor git d6b2a1709d28c656dadc019fb24145e6ac400771 + legacy/trac#13161
chutney git 60b2d18d81904e6a71a352dfa8b5cb73f4e04003 + legacy/trac#13161
= Extra chutney configs
== 10-chutney-basic-middle.patch
Now that we have middle relays (relay.tmpl) and exits (exit.tmpl) from chutney-explicit-exit.patch in legacy/trac#13161, configure a network with middle & exit routers.
== 11-chutney-large-huge.patch
Add new large and huge chutney configs. Depends on chutney-explicit-exit.patch in legacy/trac#13161Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13934Hidden service torrc template and network configuration2020-06-27T13:19:05ZDavid Gouletdgoulet@torproject.orgHidden service torrc template and network configurationAttached is a patch for HS support in chutney.
The size of the network is a bit bigger than usual because I needed a more nodes for performance measurements. Easy command to use it:
`chutney start networks/hs`
hs --> goes in networks/...Attached is a patch for HS support in chutney.
The size of the network is a bit bigger than usual because I needed a more nodes for performance measurements. Easy command to use it:
`chutney start networks/hs`
hs --> goes in networks/
hs.tmpl --> goes in torrc_templates/Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13935Issue with HS availability2020-06-27T13:19:05ZDavid Gouletdgoulet@torproject.orgIssue with HS availabilityIt takes around 40 to 45 seconds for a client of the chutney network to be able to reach an hidden service.
My first guest would be to look at the upload period of the HS descriptor. I can see in the logs that the HSDir simply doesn't h...It takes around 40 to 45 seconds for a client of the chutney network to be able to reach an hidden service.
My first guest would be to look at the upload period of the HS descriptor. I can see in the logs that the HSDir simply doesn't have the descriptor when the client is trying to fetch it.
This can be reproduced by using the "patch" in legacy/trac#13934Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13956Remove old configuration files before configuring2020-06-27T13:19:05ZTracRemove old configuration files before configuringIt is very simple but i think it is useful. Before creating a new configuration it removes the old configuration files. I have already made a pull request to https://github.com/torproject/chutney
**Trac**:
**Username**: huigIt is very simple but i think it is useful. Before creating a new configuration it removes the old configuration files. I have already made a pull request to https://github.com/torproject/chutney
**Trac**:
**Username**: huigNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13980Added new script for warnings in chutney's logs2020-06-27T13:19:05ZTracAdded new script for warnings in chutney's logsIn chutney's repository in the TODO file there was a comment about doing a script for getting warnings in the logs. The script is at https://github.com/huig-/chutney and i made a pull request days ago (see https://trac.torproject.org/pro...In chutney's repository in the TODO file there was a comment about doing a script for getting warnings in the logs. The script is at https://github.com/huig-/chutney and i made a pull request days ago (see https://trac.torproject.org/projects/tor/ticket/13956#ticket) with a different change but now it also includes the script about warnings. The script basically gets warnings int net/nodes/*/info.logs and counts how many times each warning occurs. I have also added an option to get the warnings of only one node (specified by the user) instead of all of them.
The script is called warnings.sh
**Trac**:
**Username**: huigNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/13984Added new script for getting hs addresses in chutney2020-06-27T13:19:05ZTracAdded new script for getting hs addresses in chutneyThe script outputs the hidden services onion addresses in chutney. It is simple but I was told it would be useful. The script is at https://github.com/huig-/chutney and it is called hsaddress.sh (tools/hsaddress.sh).
**Trac**:
**Usern...The script outputs the hidden services onion addresses in chutney. It is simple but I was told it would be useful. The script is at https://github.com/huig-/chutney and it is called hsaddress.sh (tools/hsaddress.sh).
**Trac**:
**Username**: huigNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14019Fix Python 2 issues in chutney refactor2020-06-27T13:19:05ZteorFix Python 2 issues in chutney refactorPlease merge fix-python2-issues from https://github.com/teor2345/chutney.git
This fixes:
* Brackets around print statements
* Double-opening a filePlease merge fix-python2-issues from https://github.com/teor2345/chutney.git
This fixes:
* Brackets around print statements
* Double-opening a fileNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14067chutney verify doesn't verify bridge clients or hidden services2020-06-27T13:19:05Zteorchutney verify doesn't verify bridge clients or hidden servicesThe current `chutney verify` implementation only verifies clients.
I have a patch that makes it verify bridge clients as well. (I'll post it soon.)
But I don't know how to verify a hidden service - particularly the one configured in th...The current `chutney verify` implementation only verifies clients.
I have a patch that makes it verify bridge clients as well. (I'll post it soon.)
But I don't know how to verify a hidden service - particularly the one configured in the `hs` chutney network.
dgoulet, do you have any ideas?teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14173chutney verify: verify in parallel, rather than one at a time (Tor load / per...2020-06-27T13:19:04Zteorchutney verify: verify in parallel, rather than one at a time (Tor load / performance testing)There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048...There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048.html
Simulate high Tor load https://lists.torproject.org/pipermail/tor-relays/2015-January/006203.html
It would be nice if `chutney verify` connections were done in parallel, but I don't think that's the case.
Nick, is this SponsorR, or SponsorS, or both?Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14174chutney verify: make amount of data sent configurable (Tor load / performance...2020-06-27T13:19:04Zteorchutney verify: make amount of data sent configurable (Tor load / performance testing)There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048...There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048.html
Simulate high Tor load https://lists.torproject.org/pipermail/tor-relays/2015-January/006203.html
It's possible to manually modify the amount of random data sent while verifying connectivity (look for "Octets" in chutney's TorNet.py).
But it would be nice if this amount was configurable.
Nick, is this SponsorR, or SponsorS, or both?teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14175chutney verify: report client, bridge, and HS performance2020-06-27T13:19:04Zteorchutney verify: report client, bridge, and HS performanceThere is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048...There is a need to load-test Tor relays when bringing them up, and to performance-test tor in general, whether relaying or hidden services.
See:
Tor BSD Underperformance https://lists.torproject.org/pipermail/tor-dev/2015-January/008048.html
Simulate high Tor load https://lists.torproject.org/pipermail/tor-relays/2015-January/006203.html
It would be nice to have a command for this, that would execute the same tests, and then report performance as a series of MB/s figures for clients->exits, bridge clients->exits, and clients->hidden services.
Nick, is this SponsorR, or SponsorS, or both?teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14315Update README2020-06-27T13:19:04ZcypherpunksUpdate READMECurrently the README states that Python 2.5 or later is supported. Chutney already uses features that are present in Python 2.6 and later and Python 2.6 is not maintained.
Should Python 2.7 not be the minimum version?Currently the README states that Python 2.5 or later is supported. Chutney already uses features that are present in Python 2.6 and later and Python 2.6 is not maintained.
Should Python 2.7 not be the minimum version?Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14333Document the environment variables2020-06-27T13:19:04ZcypherpunksDocument the environment variablesThe environment variables used by Chutney are hidden in the code and not documented anywhere else. The attached patch mentions them in the `README`.The environment variables used by Chutney are hidden in the code and not documented anywhere else. The attached patch mentions them in the `README`.Nick MathewsonNick Mathewson