Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I appreciate any suggestions, this is really annoying me!
hereŽ s a bit more info, when the connection freezes I can still see that it established from netstat in the other computer. Is it possible somehow to try to attach back to this connection? Anyway that wouldnt solve the actual problem but it would be nice to know too.
I am seeing the exact same thing. I haven't taken much time to debug it yet, as I'm usually in and out with ssh, rarely idle, so it doesn't pop up for me terribly often given my usage pattern.
Maybe we can compare notes. My setup:
client end: Debian Sarge, ssh version 1:3.8.1p1-8.sarge.4
server end: Debian Sid, openssh version 1:4.2p1-5 (provides ssh-server)
After only a few minutes of idle time it will lock up on me. ipconfig doesn't show any errors (checked per suggestion from macemoneta). Both client and server ends still show an ESTABLISHED connection after the lockup. New ssh connections can be created while the old one is locked up. Killing the window on the client end is the only recovery I've found for the hung client. This does not kill the process on the server end. A manual kill -9 on the connection's sshd process is required to clear the server.
I do NOT see any lockups when this same client connects to a totally different server, in my case a server running Solaris 7 (yeah, I know it's old ... not my machine though) This connection can sit idle for hours without lockup.
One thing that caught my eye when viewing netstat output on the client and server after the connection was locked: The client end was showing the ESTABLISHED connection using tcp while the server end was showing tcp6. I have no idea if this is at all relavent, but it caught my eye and I will try to look into it further to rule this out as a factor.
Have you tried with different routers and from different clients? My friend tried with ssh and putty but didnt notice freezing. I heard that in some netgear and linksys routers there is a problem which causes session freezing.
I dont right now have an opportunity to try via different routers but I will keep in touch. I want to solve this very annoying problem.