Opened 7 years ago

Closed 2 years ago

#7172 closed project (implemented)

Come up with configuration options and instructions for running private Tor networks in testing and simulation environments

Reported by: karsten Owned by: nickm
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay, testing
Cc: robgjansen, nickm, ln5, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

(Mostly re-using Roger's words for this ticket description.)

We should try to make TestingTorNetwork smoother and more reliable. That's useful for Shadow et al (Rob keeps running into bugs where his testbed network behaves funny due to TestingTorNetwork), and it would also be useful for setting up large private Tor networks for testing purposes.

#6752 is an example for problems with TestingTorNetwork. We'd probably find more such bugs if we spent some time running our own Tor networks and knowing how it's supposed to work.

Maybe this is best done by making Chutney better so we can notice problems, or maybe it's best done just by sitting down with a test Tor network, watching what goes wrong, fixing it, repeat.

The current status of Chutney is that it doesn't make any application requests to the Tor network it starts. It doesn't know how to check whether a Tor has bootstrapped correctly, has established a circuit, etc. Linus indicated that he might be interested in stabbing further at Chutney which he already did as part of the IPv6 work.

Child Tickets

TicketStatusOwnerSummaryComponent
#6752closedTestingTorNetwork doesn't lower the dir fetch retry schedulesCore Tor/Tor

Change History (13)

comment:1 Changed 7 years ago by arma

We just hit #3443 on the deter simulation. My fix was to tell them to set LearnCircuitBuildTimeout to 0 and set CircuitBuildTimeout to 60.

comment:2 Changed 7 years ago by arma

Description: modified (diff)

comment:3 Changed 7 years ago by arma

Component: ChutneyTor
Keywords: SponsorF20131101 added; SponsorZ removed

Moving out of the Chutney component, since maybe Shadow is the better way to go here since it's closer to complete.

comment:4 Changed 7 years ago by nickm

Milestone: Tor: 0.2.5.x-final

comment:5 Changed 7 years ago by nickm

Keywords: tor-relay testing added

comment:6 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:7 Changed 6 years ago by ln5

I think that the measurable ideas in the description are implemented, see #8530 and #8531.

Who can move this ticket forward by suggesting more concrete things to be done? Maybe Rob has some requests?

Another option would be to close it.

comment:8 Changed 6 years ago by nickm

I think we could call this closed, given that the chutney test-network script seems to work okay now . But let's wait a little while to see if there are more ideas we should implement.

comment:9 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:10 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:11 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:12 Changed 2 years ago by nickm

Keywords: SponsorF20131101 removed
Severity: Normal

comment:13 in reply to:  8 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.5.x-final
Resolution: implemented
Status: newclosed

Replying to nickm:

I think we could call this closed, given that the chutney test-network script seems to work okay now . But let's wait a little while to see if there are more ideas we should implement.

3 years is probably more than "a little while". Closing :)

Note: See TracTickets for help on using tickets.