I'm missing ServerAliveInterval/ClientAliveInterval in Sun's implementation
of SSH (both Solaris 9 and 10). Maybe the feature came in a newer version
of OpenSSH than the one Sun based its implementation on.

Is there a chance that this will be added? I couldn't find anything
(bug report/RFE) on sunsolve.

It helps against the annoying problem of broken ssh connections caused
by connection timeouts in NAT/FW devices.

mp.
-- 
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

HI,

Martin Paul wrote:
> I'm missing ServerAliveInterval/ClientAliveInterval in Sun's implementation
> of SSH (both Solaris 9 and 10). Maybe the feature came in a newer version
> of OpenSSH than the one Sun based its implementation on.
> 
> Is there a chance that this will be added? I couldn't find anything
> (bug report/RFE) on sunsolve.
> 
> It helps against the annoying problem of broken ssh connections caused
> by connection timeouts in NAT/FW devices.
> 
> mp.

I am not answering your question, but I have alot of broken ssh 
connections but sometimes a shell can be on for weeks between two 
machines, and then when I open a new connection it can break after a few 
seconds.

Do you have this kind of behaviour?

This is ONLY on Internet connections!

cheers

Michael

Michael Laajanen <michael_laajanen@yahoo.com> wrote:
> Martin Paul wrote:
>> It helps against the annoying problem of broken ssh connections caused
>> by connection timeouts in NAT/FW devices.
> 
> I am not answering your question, but I have alot of broken ssh 
> connections but sometimes a shell can be on for weeks between two 
> machines, and then when I open a new connection it can break after a few 
> seconds.

No, I guess that's a different problem. In my case it's reproducible - 
any connection crossing the Cisco PIX firewall is broken after exactly
one hour of idle time. AFAIK all(?) NAT devices have such (configurable)
connection timeouts to free unused connection slots. I'd prefer to fix
it on the application level, that's what ServerAliveInterval does.

Try to run "ssh -vvv <remote>" and see if you get useful information
in the debug output after the connection breaks.

mp.
-- 
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

Martin Paul <map@par.univie.ac.at> wrote:
> Michael Laajanen <michael_laajanen@yahoo.com> wrote:
> > Martin Paul wrote:
> >> It helps against the annoying problem of broken ssh connections caused
> >> by connection timeouts in NAT/FW devices.
> > 
> > I am not answering your question, but I have alot of broken ssh 
> > connections but sometimes a shell can be on for weeks between two 
> > machines, and then when I open a new connection it can break after a few 
> > seconds.
> 
> No, I guess that's a different problem. In my case it's reproducible - 
> any connection crossing the Cisco PIX firewall is broken after exactly
> one hour of idle time. AFAIK all(?) NAT devices have such (configurable)
> connection timeouts to free unused connection slots. I'd prefer to fix
> it on the application level, that's what ServerAliveInterval does.
> 
Yes, I have exactly this problem when connecting out from my Solaris
box.  I've fixed it by having the remote system start a background
task which sends a NUL character across the link every ten minutes or
so.  While this is a bit of a crude bodge it does work OK and is, as
far as a I can tell, totally transparent.  I've been using it for some
years now with no problems.

-- 
Chris Green

usenet@isbd.co.uk writes:

> Yes, I have exactly this problem when connecting out from my Solaris
> box.  I've fixed it by having the remote system start a background
> task which sends a NUL character across the link every ten minutes

Someone found these disconnections that they wrote a program that
produces screen output:

http://www.laffeycomputer.com/spinner.html

-- 
David Magda <dmagda at ee.ryerson.ca> 
Because the innovator has for enemies all those who have done well under 
the old conditions, and lukewarm defenders in those who may do well 
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI 

David Magda <dmagda+trace050401@ee.ryerson.ca> wrote:
> usenet@isbd.co.uk writes:
> 
> > Yes, I have exactly this problem when connecting out from my Solaris
> > box.  I've fixed it by having the remote system start a background
> > task which sends a NUL character across the link every ten minutes
> 
> Someone found these disconnections that they wrote a program that
> produces screen output:
> 
> http://www.laffeycomputer.com/spinner.html
> 
Yes, "spinner -n" does just about exactly what I do.

-- 
Chris Green