Feb 14 10:37:46.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
We recently changed the bootstrap percentages and messages in Tor.Please paste the log lines that containing these bootstrap messages.And any error messages near those lines.
Is this optional, are there alternative ways of measuring bandwidth?
To get good bandwidth numbers, you'll need to pass some trafficthrough your network. To get measured bandwidth in the votes,you'll need to run a bandwidth authority, like sbws:
I pasted one of the microdescriptors at the end of the message (it's fetched from one of the authorities).It would help to know what's actually in the consensus. (See below.)
It is definitely shut down when I start deleting the files.
Maybe there's a bug in ShutdownWaitLength.We changed that code recently.Is Tor actually shut down when you remove the files?
I followed your idea of defining and deleting directories so now there are data/ cache/ and keys/ defined in the torrc and this is what I remove in the cleanup procedure. I keep the keys dir, the stats file, and the fingerprint file. The issue with old Guard entries in the new state file remains.
When you start Tor, what is actually in the data directory?
One of the microdesc files is pasted below. I see the Running flag set for several relays, along with Fast, Guard, and sometimes also Exit (for example, relay08 is defined as exit in the torrc and also shows up as Exit Fast Guard HSDir Running Stable V2Dir Valid).
tor/server/all is a list of all relay descriptors that the authority knows about.
But the consensus is different: it contains the relays from the authorities'votes, but only if those relays are reachable from the authorities(the Running flag), and the authorities agree on enough info about therelays.
Please check the votes and consensuses on each authority:http://<hostname>/tor/status-vote/current/authorityhttp://<hostname>/tor/status-vote/current/consensushttp://<hostname>/tor/status-vote/current/consensus-microdesc
Yes, and this is exactly what I need to measure in the private network. My project is about testing the consequences of the DoS features in relays and how the client reacts to being blocked (if it recognizes this at all, that's one of the things I want to find out).
That's not how Tor works:
Clients randomly select relays from the consensus.
It's just a simple extendcircuit 0 FP,FP,FP,... for testing the network status. If the network starts functioning normally again, I need to use either NEWNYM via the controlport or stem and new_circuit(). But right now I don't get to this point, because NEWNYM results in no new circuit and also the stem implementation does not deliver new circuits. Just to give an example:
Can you copy and paste the code you're using?
I'm pretty much sure I delete the file and that there are no .new versions of the state file. Still, after a while the old Guards show up in the state file. What information is used to generate the state file? Maybe there is still some kind of cache left somewhere else?
The dates are the time when Tor chose the guard.Maybe you're not actually deleting the state file?Maybe there's an undocumented state.new file?
Great idea, did that! Nothing but the keys and fingerprint in there, as described above.
What's in the directory after you run the script?
Removing specific files is inherently fragile: future Tor versionsmay add new files.
Instead, configure different directories for CacheDirectory,DataDirectory, and KeyDirectory. Then, delete and re-createCacheDirectory and DataDirectory. Fail and refuse to start Torif the deletion and re-creation fails.
Yes you did and things are getting clearer :)I think I answered these questions above in context.
Yes, the setup is still not in the state where the client is able to create "natural" circuits.
Let me know if you're still having trouble.