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
wit
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
On Wed, Feb 19, 2014 at 6:53 PM, Sebastian Urbach wrote:
> 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 03/2014. Multiple run's from the same ip are very
> welcome as well.
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
On 2/19/14, Zenaan Harkness wrote:
> On 2/19/14, Alexander Makarov 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 home ADSL2 connection, but off-net, s
