For future reference, in case anyone is interested, switching out tsocks
for the more complicated dante-client makes svn http:// through socks 5
run perfectly.
On 19/07/13 09:56, Øyvind 'bolt' Hvidsten wrote:
Testcase:
------------------------------------------------------------------------------
apt-get install tsocks
export TSOCKS_CONF_FILE="$HOME/.tsocks.conf"
cat - >"$HOME/.tsocks.conf" <<EOF
server = 127.0.0.1
server_port = 1080
server_type = 5
local = 192.168.0.0/255.255.0.0
local = 172.16.0.0/255.240.0.0
local = 10.0.0.0/255.0.0.0
EOF
ssh localhost -D 1080
<start tcpdump on favorite network interface>
tsocks svn co http://opkg.googlecode.com/svn/trunk/
------------------------------------------------------------------------------
On 19/07/13 09:44, Øyvind 'bolt' Hvidsten wrote:
I am trying to access several subversion repositories from behind a
socks proxy. Client machine runs Debian Linux. I use tsocks to stuff svn
into the proxy. I can do "tsocks svn co svn://blah.." just fine through
the proxy, but "tsocks svn co http://blah.."; hangs for a long time and
then says "Could not read status line: connection was closed by server".
I also tried from an unrestricted network, with ssh -D to localhost to
set up a quick socks proxy. Same error when using tsocks. Without the
proxy, the repo works fine.
I can see in wireshark that with tsocks it asks for OPTIONS, as without
a proxy, gets the OPTIONS back, as without a proxy, and then it just
sits there, sending no further data until the error apprears and it
exits.
In the restricted network, the SOCKS proxy is dante, but as I mentioned,
the same situation occurs with a simple ssh -D proxy.
I've tested that in both cases, "tsocks wget ...." works perfectly.
Using http://opkg.googlecode.com/svn/trunk/ for testing, but I've tried
several others too.
Any ideas?
