[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #16386 [Chutney]: Chutney generates network with no bandwidth weights
#16386: Chutney generates network with no bandwidth weights
-------------------------+-------------------
Reporter: asn | Owner: nickm
Type: defect | Status: new
Priority: normal | Milestone:
Component: Chutney | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------
Comment (by teor):
Hi asn,
Setting these flags on every relays was a part of the rapid bootstrap
changes that I made in #13163 and related issues.
You're right, it would be great to be able to select parts of the network
for these flags.
I can imagine this feature being implemented like this:
{{{
TestingDirAuthVoteExit m-n
TestingDirAuthVoteGuard p%-q%
}}}
This would vote relays `m` to `n` (by fingerprint) as Exits, and relays
`p%` to `q%` as Guards. We'd probably want to make a similar change to the
corresponding `TestingDirAuthVoteHSDir` flag as well, even if we didn't
use it.
We could implement this feature in chutney or in tor:
* In chutney, we could perhaps do this as part of the templating system,
or maybe it could wait for chutney 2?
* In tor, we could allow the `TestingDirAuthVote...` parameters to take a
`m-n` or `p%-q%` argument, by modifying `routerset_contains_routerstatus`.
I'd want to ensure this was only active in test networks, of course.
I am in favour of making this change in tor, where it might assist a wider
range of users. And it would work in chutney 2 for free. But I'd want to
get nickm's advice.
What do you think?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16386#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs