Menu
▾
▴
[privoxy-users] [ ijbswa-Support Requests-2005676 ] Gajim hangs on connection to Privoxy (as a SOCKS5 proxy)
|
From: SourceForge.net <no...@so...> - 2008-06-29 12:26:12
|
Support Requests item #2005676, was opened at 2008-06-29 06:51 Message generated for change (Comment added) made by fabiankeil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2005676&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: other Group: 3.0.8 >Status: Closed Priority: 5 Private: No Submitted By: Marcin Zajaczkowski (szpak) >Assigned to: Fabian Keil (fabiankeil) Summary: Gajim hangs on connection to Privoxy (as a SOCKS5 proxy) Initial Comment: I'm unable to make Gajim use Privoxy as a proxy (to work with Tor). I'm not sure if this issue is caused by Prixovy (it proxies without any problem traffic from Firefox and ssh), but also Gajim works fine with "ssh -D" and pure Tor as a SOCKS5 proxy. The issue is that Gajim "hangs" when trying to connect to Privoxy. At its 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 authentification DEBUG: CONNECTproxy sent Privoxy with maximum debug shows only: Jun 29 00:31:02.580 Privoxy(b7f3b6c0) Connect: accepted connection from 127.0.0.1 Jun 29 00:31:02.611 Privoxy(b7f3b6c0) Connect: Listening for new connections ... It would suggest that Gajim "hangs" before sending any "real" request: I have checked it at TCP level (with tcpdump) and it looks like (szpak is a hostname): 23:55:35.994463 IP szpak.45365 > szpak.privoxy: S 580179035:580179035(0) win 32792 <mss 16396,sackOK,timestamp 12080872 0,nop,wscale 6> 23:55:35.994519 IP szpak.privoxy > szpak.45365: S 580266575:580266575(0) ack 580179036 win 32768 <mss 16396,sackOK,timestamp 12080872 12080872,nop,wscale 6> 23:55:35.994553 IP szpak.45365 > szpak.privoxy: . ack 1 win 513 <nop,nop,timestamp 12080872 12080872> 23:55:35.996639 IP szpak.45365 > szpak.privoxy: P 1:5(4) ack 1 win 513 <nop,nop,timestamp 12080874 12080872> 23:55:35.996714 IP szpak.privoxy > szpak.45365: . ack 5 win 512 <nop,nop,timestamp 12080874 12080874> 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)? Maybe you see any other reason (also at Gajim side) why it doesn't work? I can also provide more detailed dump from wireshark If needed. Test environment: Privoxy 3.0.8 Fedora 8 Gajim snapshot 2008-06-29 It can be easily reproduced with Gajim snapshot (latest stable release doesn't have SOCKS5 support yet) which can be downloaded from: http://www.gajim.org/downloads/snap/ Thanks for help Marcin ---------------------------------------------------------------------- >Comment By: Fabian Keil (fabiankeil) Date: 2008-06-29 12:26 Message: Logged In: YES user_id=875547 Originator: NO Privoxy is a HTTP proxy and doesn't support incoming SOCKS connections. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2005676&group_id=11118 |