ssh connections dropping

I have pretty much the same problem. On my Power Mac running Mountain Lion, an ssh connection to a remote computer with Terminal gives the error 'Write failed: Broken pipe" after a few minutes. However on my Power Book running Tiger on the same local network, there is no problem at all. Apple needs to address this and several other problems.

I suspect this occurs when the remote-connected machine goes on stand-by, without checking if a ssh connection does exist. This is clearly a bug appeared in the few latest releases of Mac OS. REALLY annoying...

Okay. So this was driving me absolutely nuts!!! I am a network admin and I purchased a new MacBook and I couldn't keep an SSH session alive for more than like 10 seconds without getting a broken pipe to any of about a thousand devices I have access to.

I have tried a million things and I FINALLY fixed this. I hope this helps everyone else out there with this problem that couldn't find a solution. I changed my client side (MacOS X) SSH keepalive to an insanely high number. Seems to have done the trick. It also seems to have fixed connectivity problems between other protocols as weel, such as RDP. I do not use RDP as frequently but I was having connectivity problems there as well that seem to have been rectified.

I hope this helps!

sudo sysctl -w net.inet.tcp.always_keepalive=xx

In my case, sudo sysctl -w net.inet.tcp.always_keepalive=9999

kr4m17...does this line go into my .bash_profile?

Hopefully this will fix my issue...I'm having lots of broken pipes when using scp.

Thanks.

No, just run that from your terminal. Let me know how it works out. I have fixed a whole lot of my broken pipes with this. It still isn't perfect, but I can use my systems now... Hope this helps.

I have the same problem. Tried your solution, kr4m17. Unfortunately, it didn't work for me.

adding ServerAliveInterval 60 to ~/.ssh/config worked.

Thanks this worked for me!

kr4m17 wrote:

Okay. So this was driving me absolutely nuts!!! I am a network admin and I purchased a new MacBook and I couldn't keep an SSH session alive for more than like 10 seconds without getting a broken pipe to any of about a thousand devices I have access to.

I have tried a million things and I FINALLY fixed this. I hope this helps everyone else out there with this problem that couldn't find a solution. I changed my client side (MacOS X) SSH keepalive to an insanely high number. Seems to have done the trick. It also seems to have fixed connectivity problems between other protocols as weel, such as RDP. I do not use RDP as frequently but I was having connectivity problems there as well that seem to have been rectified.

I hope this helps!

sudo sysctl -w net.inet.tcp.always_keepalive=xx

In my case, sudo sysctl -w net.inet.tcp.always_keepalive=9999

THANK YOU!

I'm running Mavericks 10.9.5 and this worked for me.

sudo sysctl -w net.inet.tcp.always_keepalive=9999

I wonder if this will need to be applied after any system updates?

eric