[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: WinXP_client_problem



Hi alien,

Wednesday, August 31, 2005, 1:09:45 PM, you wrote:

> Aug 31 12:41:28.093 [Notice] Tor has successfully opened a
> circuit. Looks like it's working.
> Aug 31 12:41:28.109 [Notice] Now checking whether ORPort and
> DirPort are reachable... (this may take several minutes)
> Aug 31 12:41:43.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:41:43.718 [Notice] circuit_log_path(): exit circ
> (length 3): metropipeII(open) moria1(open) afflictions(open)
> Aug 31 12:41:50.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:41:50.718 [Notice] circuit_log_path(): exit circ
> (length 3): metropipeII(open) moria1(open) afflictions(open)
> Aug 31 12:41:58.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:41:58.718 [Notice] circuit_log_path(): exit circ
> (length 3): DSENET(open) lysander(open) ctcryptlord(open)
> Aug 31 12:42:05.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:42:05.718 [Notice] circuit_log_path(): exit circ
> (length 3): DSENET(open) lysander(open) ctcryptlord(open)
> Aug 31 12:42:13.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:42:13.718 [Notice] circuit_log_path(): internal
> (high-uptime) circ (length 3): mushin(open) random(open) ned(open)
> Aug 31 12:42:20.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:42:20.718 [Notice] circuit_log_path(): internal
> (high-uptime) circ (length 3): mushin(open) random(open) ned(open)
> Aug 31 12:42:28.718 [Notice] connection_ap_expire_beginning():
> Stream is 15 seconds late on address '[scrubbed]'. Retrying.
> Aug 31 12:42:28.718 [Notice] circuit_log_path(): exit circ
> (length 3): athenathegoddess(open) winnie(open) inap1(open)
> Aug 31 12:42:28.718 [Notice] Tried for 63 seconds to get a
> connection to [scrubbed]:80. Giving up.
>
> It will build endlessly like this and periodically I get a
> "not managed to confirm its ORPort/DirPort reachable".
>
> I've tried the obvious stuff such as bypassing firewalls but its not
> it. Tried 0.1.0.14 and 0.1.1.5-alpha, changing ports, restarting,
> nothing works. Mysteriously, there were brief times when everything
> went alright but it's been a couple of days that I simply can not
> connect as server. I've never had an outage like this for so long.
>
> I can't make anything useful from the debug log, would it help if I
> posted it here?

I might have found the reason but I need to understand how the network
acknowledges that a Tor server has changed its IP. How soon will the
network realize this? Is it possible that due to some sort of lag the
network might think a server is sitting on the old IP when in fact it
has changed?

-- 
cheers!
 alien  mailto:alien51@xxxxxxxxxxxx

.. On the other hand, you have different fingers.