i ssh into my home machine from work pretty frequently. the connection at work is a T1 and the home connection is a cable modem. the problem is that when i run commands, it hangs on output.

for example, if i try to cat something, half the output is shown before it freezes and doesn't respond to any input. same thing happens if i try to compile stuff, run vi, run top, basically anything that has a decent amount of output. usually, when i relogin, i find that the command ran to completion, its just that my ssh session froze up on the output.

what can i do to alleviate the problem? its such an annoyance to have to relogin all the time.

thanks for the help.

I am guessing if you run ssh over your local network it won't be a problem right? It is probably due to your cable service. SSH is very picky about recieving packets and when the data level is increased your cable services is probably dropping too many of the packets and ssh gets pissed off.

intersting, thanks for the reply. so there is no way to remedy this? can't relax ssh's packet dropping policy?

and yes you are correct, if i run ssh thru my LAN, everything works great...as if i was at that machine's tty.

I ran into this problem on my server that resides on Georgia Tech's campus. Fortunately they were sympathetic to my needs (and the admins there use SSH as well) and they cranked up the priority on SSH packets and cranked down the priority of p2p packets (which was what cause the jam in the first place) and fixed the problem. I am not sure there is anything you can do short of begging the cable people to fix the problem.