Chutney issueshttps://gitlab.torproject.org/tpo/core/chutney/-/issues2020-06-27T13:19:08Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/6413Add support for bridges and clients on IPv6 to chutney2020-06-27T13:19:08ZLinus Nordberglinus@torproject.orgAdd support for bridges and clients on IPv6 to chutneyBranch ipv6-bridges in user/linus/chutney.git contains support for
bridges on IPv6 and clients using them.Branch ipv6-bridges in user/linus/chutney.git contains support for
bridges on IPv6 and clients using them.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/6753chutney needs to set AlternateBridgeAuthority too2020-06-27T13:19:08ZRoger Dingledinechutney needs to set AlternateBridgeAuthority tooSince git commit 21c6c8485 (to Tor), Tor won't start if TestingTorNetwork is on, AlternateDirAuthority is set, but AlternateBridgeAuthority is not.Since git commit 21c6c8485 (to Tor), Tor won't start if TestingTorNetwork is on, AlternateDirAuthority is set, but AlternateBridgeAuthority is not.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/6754chutney traceback when it can't kill its tors fast enough2020-06-27T13:19:07ZRoger Dingledinechutney traceback when it can't kill its tors fast enough```
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globa...```
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/arma/old/torgit/chutney/lib/chutney/TorNet.py", line 663, in <module>
main()
File "/home/arma/old/torgit/chutney/lib/chutney/TorNet.py", line 660, in main
runConfigFile(sys.argv[1], f)
File "/home/arma/old/torgit/chutney/lib/chutney/TorNet.py", line 646, in runConfigFile
getattr(network,verb)()
File "/home/arma/old/torgit/chutney/lib/chutney/TorNet.py", line 619, in stop
n.check(listNonRunning=False)
AttributeError: 'int' object has no attribute 'check'
```Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/8531Extend Chutney to be able to verify that we can send and retrieve traffic2020-06-27T13:19:07ZLinus Nordberglinus@torproject.orgExtend Chutney to be able to verify that we can send and retrieve trafficThis is related to legacy/trac#8530.This is related to legacy/trac#8530.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/9086Rewrite network testing using asyncore/asynchat2020-07-17T11:01:53ZLinus Nordberglinus@torproject.orgRewrite network testing using asyncore/asynchatAs Nick points out in legacy/trac#8531, we should use asyncore or maybe even
asynchat for the network testing in Traffic.py.
This will give us more readable code and higher code quality.As Nick points out in legacy/trac#8531, we should use asyncore or maybe even
asynchat for the network testing in Traffic.py.
This will give us more readable code and higher code quality.https://gitlab.torproject.org/tpo/core/chutney/-/issues/9087Move network tests out of TorNet.py2020-06-27T13:19:07ZLinus Nordberglinus@torproject.orgMove network tests out of TorNet.pyAs Nick points out in legacy/trac#8531, it's far from perfect that new network
tests need to go into TorNet.py.
Maybe read a config file or pick up .py files from a tests/ directory?As Nick points out in legacy/trac#8531, it's far from perfect that new network
tests need to go into TorNet.py.
Maybe read a config file or pick up .py files from a tests/ directory?https://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/10155Allow delayed node start2020-07-17T11:02:21ZMatthew FinkelAllow delayed node startIt will be useful to allow nodes to be started after a certain amount of time, especially when interested in its effect on the consensus.It will be useful to allow nodes to be started after a certain amount of time, especially when interested in its effect on the consensus.https://gitlab.torproject.org/tpo/core/chutney/-/issues/10156Replace DirServer with DirAuthority in torrc2020-07-23T20:05:23ZMatthew FinkelReplace DirServer with DirAuthority in torrcShould the generated torrc use DirAuthority instead of DirServer now that legacy/trac#6791 and legacy/trac#10124 are merged into Tor? It'll probably be smart to have an option to tell Chutney to use DirServer if one tests with an older v...Should the generated torrc use DirAuthority instead of DirServer now that legacy/trac#6791 and legacy/trac#10124 are merged into Tor? It'll probably be smart to have an option to tell Chutney to use DirServer if one tests with an older version.https://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/11374fix tor lockfile checking bug2020-07-23T20:06:47ZTracfix tor lockfile checking bugI previously had a misconception that lockfile got removed every time tor exits :(
This patch checks the state of lockfile properly.
branch:
https://github.com/houqp/chutney/tree/lock_fix
**Trac**:
**Username**: dave2008I previously had a misconception that lockfile got removed every time tor exits :(
This patch checks the state of lockfile properly.
branch:
https://github.com/houqp/chutney/tree/lock_fix
**Trac**:
**Username**: dave2008https://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/13887Pick a reporting format for Chutney2020-07-23T20:07:43ZNick MathewsonPick a reporting format for ChutneyWe need some way for Chutney to tell another process about the events it's seeing.
Options include CTF, json, protocolbufs, line-based text.
See https://lists.torproject.org/pipermail/tor-dev/2014-December/007898.html for a synopsis of...We need some way for Chutney to tell another process about the events it's seeing.
Options include CTF, json, protocolbufs, line-based text.
See https://lists.torproject.org/pipermail/tor-dev/2014-December/007898.html for a synopsis of goals.
I'm especially interested in dgoulet's opinion on CTF in particular.
I'm especially interested in atagar's opinion about what would be friendliest to a stem-based chutney.https://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 Mathewson