Marcin Zajączkowski wrote:
> On 2008-06-15 09:12, Yann Leboulanger wrote:
>> Marcin Zajączkowski wrote:
>>> Thank you for your answer Yann.
>>> I checked my Gajim with ssh -D (I didn't even know about that option to
>>> get SOCKS5 proxy) and it was fine. I have also checked it with pure Tor
>>> and it worked either. It seems to be an issue with privoxy itself.
>>> I'm a little bit astonish, because a few other apps work with privoxy
>>> without any problem. I will try to debug it on the privoxy side.
>> Ok, thanks for trying to make it work ! Please keep us informed of your
> Hello again,
> Today I was debugging the problem at the privoxy side and it seems that
> gajim hangs at the beginning of the conversation, before sending any
> "real" data.
> At gajim side it looks like (gajim.py -v):
> DEBUG: CONNECTproxy start Plugging
> <common.xmpp.transports_nb.NBSOCKS5PROXYsocket instance at 0x98015cc>
> into <common.xmpp.client_nb.NonBlockingClient instance at 0x904e08c>
> DEBUG: CONNECTproxy start Proxy server contacted, performing
> DEBUG: CONNECTproxy sent
that's strange that nothing is sent here. re-reading the code, here
connector is suppose dto be sent. It's a base64 encoded string, and then
we wait for the answer.
> tcpdump shows following traffic on lo (szpak is a hostname):
> In the communication with pure Tor there is one more packet PSH,ACK from
> Tor, which is confirmed by Gajim and next Gajim sends its request.
> I'm not a TCP expert, but do you thing the lack of that one PSH packet
> can cause that ACK is not push to Gajim and it waits for ACK forever (or
> at least until a timeout)?
> I have more detailed dump from Wireshark if someone is interested.
Maybe full sent/reveiced chars could help
Gajim-devel mailing list