Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Issue with SSH Proxy Tunneling
December 4, 2012, 2:09 pm
rate this thread
d and inactive...
I recently changed internet providers from a cable connection (3mbps/768mbp=
s) to a VDSL2 line (40mbps/20mbps) and now I find that I cannot reliably us=
e ssh to tunnel web traffic. Regular ssh terminal session will stay open i=
ndefinitely, as will the session that are acting as a proxy (either static =
or dynamic), as long as they are not used to proxy traffic.
I will open a connection using like so, 'ssh -D 8080 -N <host>' and set bro=
wser proxy to 127.0.0.1 on port 8080 with SOCKSv5 checked. This is the same=
as I was previously using. Only now it will only proxy one or two web page=
requests before freezing up and eventually disconnecting the ssh session. =
When run with an additional '-vvv' I will see output like this, just as th=
e session hangs and disconnects.
debug2: channel 21: pre_dynamic: need more
debug2: channel 21: pre_dynamic: have 0
debug2: channel 21: pre_dynamic: have 27
debug2: channel 21: decode socks5
debug2: channel 21: socks5 post auth
debug2: channel 21: dynamic request: socks5 host img.gawkerassets.com port =
80 command 1
debug2: channel 7: rcvd eof
debug2: channel 7: output open -> drain
debug2: channel 7: obuf empty
debug2: channel 7: close_write
debug2: channel 7: output drain -> closed
debug2: channel 7: read<=3D0 rfd 12 len 0
debug2: channel 7: read failed
debug2: channel 7: close_read
debug2: channel 7: input open -> drain
debug2: channel 7: ibuf empty
debug2: channel 7: send eof
debug2: channel 7: input drain -> closed
debug2: channel 7: send close
debug3: channel 7: will not send data after close
I have tried so many things to fix this. I have setup a tinyproxy on the ta=
rget system and used '-L' instead of a dynamic tunnel and the same thing. =
I updated the ssh binaries on both ends to the latest version, 6.1p1. I add=
ed the patches for HPN-SSH <http://www.psc.edu/index.php/hpn-ssh and recom=
piled. I tried setting ulimit to unlimited. All to no avail.
I am not even really sure what is causing this issue and as I stated before=
, I never really saw this on my previous, slower connection. With the slowe=
r, cable connection, the most I ever saw was the occasional 'channel 1: ope=
n failed: administratively prohibited: open failed'
At this point I am open to any and all suggestions as I have failed to find=
anything on the web thus far that appears to be a similar problem to mine.
Now, a question of etiquette: as I pass, do I give you the ass or the crotc=
h?- Tyler Durden
"Be Impeccable with your Word - Don't Take Anything Personally - Don't Make=
Assumptions - Always Do Your Best"
Re: Issue with SSH Proxy Tunneling
bps) to a VDSL2 line (40mbps/20mbps) and now I find that I cannot reliably
use ssh to tunnel web traffic. Regular ssh terminal session will stay open
indefinitely, as will the session that are acting as a proxy (either stati
c or dynamic), as long as they are not used to proxy traffic.
Exact same thing here for me. I've changed my ISP to a much faster one and
the SOCKS tunnel stopped working. When debugging ssh with -vv, there is sim
ilar output to Timm's, it varies though. Sometimes the web page comes throu
gh after a while but mostly not. I've tried lowering the MTU on the server
side but it did not help. It is also worth mentioning that the ssh connecti
on itself becomes unresponsive for some time after I make a request, otherw
ise it is working very fast and with no problems.
I'll be grateful for any input on this, thanks,
- » Extend configuration in ssd_config for PermitRootLogin
- — Previous thread in » Secure Shell Forum
- » protocol question - issue with exit-status inside unfinished data stream?
- — Newest thread in » Secure Shell Forum