Oh, interesting thing. Im looking at Vidalia Network map and see something unexpected. I will explain it in points:<br><br>1) (my app) Create circuit<br>2) (vidalia) Circuit looks opened, OK<br>3) (my app) attaching stream to circuit<br>
4) (vidalia) final IP and port appears under correct circuit, status is "Connecting"<br>5 (vidalia) after few seconds, status is change to "Repeat" (there is no interaction in my app, no event, nothing)<br>
6) (vidalia) after few seconds (tell 15), status is "Closed" (and my app receive closed event of stream, which Im waiting for connect).<br><br>I see statuses in my language, so Im sorry if "Connecting" and "Repeat" are bad translations. But I dont know, why Tor cannot connect final destination, because in Vidalia it seems to do so.<br>
<br>I will be very happy for any help.<br>Marek<br><br><div class="gmail_quote">2008/12/6 slush <span dir="ltr"><<a href="mailto:slush@centrum.cz">slush@centrum.cz</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I will post final solution after it will works. Currently there is at least one problem, because after calling attach_stream from another thread (and Tor returns me SENTCONNECT event), calling of socket.connect() is still blocking and Tor never send me SUCCEEDED (which I expect as confirmation of SENTCONNECT). I'm right? What can I do wrong?<br>
</blockquote></div><br>