Hi!
Thanks for your explanation.
On 22.01.2017 16:54, Ivan Markin wrote:
This may not be related to this issue.
Yes, it looks like.
"clock jump" may not be a clock jump actually. E.g. one can just "pause" all TCP connections for some time (e.g. on a firewall/DPI/traffic shaper) and then resume them. In such case tor will regard this
That might be possible. There is no special FW rule, but the router also uses traffic shaping.
sleep/resume in the main loop as a "clock jump" thus breaking all circuits. This is because it produces ticks each second in the same thread as the main loop (which is blocking awaiting for data on a socket). There should be a ticket for this, maybe someone can arrange it.
It doesn't seem to hurt now. I will keep an eyes on it.
Regards
-- Ivan Markin