SSH Degradation

[maltheus]

I'm able to connect to my home box from work via SSH, but there's a lag in how long it takes for each character to echo back. Eventually, the client drops the connection after receiving a large amount of data.

I once had this problem before and I was certain it was the client because I could SSH just fine from within my home network and even at work, I had no problems SSHing in from a Solaris box. I looked heavily into reverse DNS issues, but that doesn't seem to be my problem. Eventually, I got a new server and rebuilt things from the ground up and to my surprise, that fixed it, for about one month. Then it started happening again.

Here's my sshd_config:

Port 8032
ServerKeyBits 2048
SyslogFacility AUTH
LogLevel INFO
LoginGraceTime 60
PermitRootLogin no
RSAAuthentication no
PubkeyAuthentication yes
PasswordAuthentication yes
PermitEmptyPasswords no
Compression yes
KeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 4

Protocol 2

UsePAM yes

UseDNS no

Subsystem sftp /usr/lib64/misc/sftp-server


Any ideas are appreciated.I even tried rebuilding the entire system using two "emerge -e system" followed by an "emerge -e world", hoping to duplicate the result I had from building the server from the ground up. Nothing seems to work. Does anyone know of any good ssh alternatives out there?

[Wormo]

I doubt the problem is really the fault of your ssh server, since it works fine from local net and from another outside host. It is weird that things temporarily worked after rebuilding your server, but don't rule out coincidence because sometime they happen...

Until very recently I've suffered through frequent disconnects when going from one of our client's network to the server for my own office, and as suspected it turned out to be a network problem, not the fault of the desktop or the server. The main router for that site is a linksys router that had firmware with buggy NAT support. Finally a coworker of mine discovered the NAT bug documented in linksys release notes and the local IT guy upgraded the router.

Also note that the buggy linksys messed up the connections from certain addresses more than others, so while networking worked almost ok on one workstation, a laptop plugged in next to it could have connections to internet totally hosed up.

[maltheus]