Re: [tor-relays] [WARN] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.

2014-02-19 Thread Zenaan Harkness
On 2/19/14, Zenaan Harkness z...@freedbms.net wrote: On 2/19/14, Alexander Makarov ice.turbul...@gmail.com wrote: Could you show the log? Current and previous tor logs attached. What is also interesting is IP address seems to change rather frequently from the ISP (iiNet in this case - a

[tor-relays] TTTT, multiple runs

2014-02-19 Thread Sebastian Urbach
Dear list members, The multiple runs question is now added to the FAQ at the Trying Trusted Tor Traceroutes project site. Right now we are at 95 ip's with at least 1 completed run. Hopefully we can add another 5 to that number and reach the 100 milestone before the next data review in

Re: [tor-relays] TTTT, multiple runs

2014-02-19 Thread Sebastian Urbach
Hi Sanjeev, Basically yes. Here are the details: http://web.engr.illinois.edu/~das17/tor-traceroute_v1.html#q-canrunelsewhere Feel free to ask if anything is unclear. -- Mit freundlichen GrĂ¼ssen / Sincerely yours Sebastian Urbach -- Those who would

Re: [tor-relays] [WARN] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.

2014-02-19 Thread grarpamp
Since you say it repeats you oppurtunity to check the system clock first: - configure tor to syslog - send an ntpdate -q pool to syslog every 5min, remove when solved. - send *.* to /var/log/all and see what you find around where the date lines start to slide or jump past each other. Graph it