Hi Jeroen,
On 09/11/2013 02:21 PM, Jeroen Massar wrote:
What else is there to tune except for maybe running multiple Tor nodes on the same box? Which would require it to use multiple IPs right as one can only run 2 nodes on the same IP I understand.
You will start to see error messages in your logs. It is very unlikely that you will be able to satisy the interface with just one Tor process. Best I've seen is 400 MBit/s per Tor process on modern machines with AES-NI.
How long did you leave your relay up and running? Let me quote from Roger's recent great blog post:
"A new relay, assuming it is reliable and has plenty of bandwidth, goes through four phases: the unmeasured phase (days 0-3) where it gets roughly no use, the remote-measurement phase (days 3-8) where load starts to increase, the ramp-up guard phase (days 8-68) where load counterintuitively drops and then rises higher, and the steady-state guard phase (days 68+)."
https://blog.torproject.org/blog/lifecycle-of-a-new-relay
Would there maybe be a way to run multiple Tor processes with the same key/identity but with a TCP load-balancer in front of it which distributes the incoming connections to the processes? The only thing then is that only one of them should report their details to the authorities and the others should not publish; would that be possible or would it mess up for instance performance stats?
I have not tried such a thing, and I don't think anyone else has. It's very easy to run and manage multiple Tor processes, and so far every ISP was able to provide more than one IP.
Great effort, thanks! Please keep it up!