[kwlug-disc] kwlug-disc Digest, Vol 31, Issue 39

[Marcel Gagne]

Hello Chris, 

This happens on a lot of routers to a lot of servers. If you haven't already done so (can't see it in the threads), open up your ssh_config file (in /etc/ssh) and add the following line. 

ServerAliveInterval 120 

Or 60 or something like that. Similarly, on the server side, you can edit the sshd_config file and add the following. 

ClientAliveInterval 120 

The idea here is that the client, or server, will send a message over the SSH connection every 120 seconds (or 60 seconds or whatever) thereby making sure the connection doesn't time out. For the server side, you obviously need to restart sshd for the changes to take effect. 

Take care out there. 

-- 
Marcel Gagné 
Salmar Consulting Inc. : 519-772-7742 
55 King Street West, 7th Floor 
Kitchener, Ontario, N2G 4W1 
Note: This massagee wos nat speel or gramer-checkered. 

----- Original Message -----

> From: kwlug-disc-request at kwlug.org
> To: kwlug-disc at kwlug.org
> Sent: Thursday, June 30, 2011 12:00:01 PM
> Subject: kwlug-disc Digest, Vol 31, Issue 39

> Today's Topics:

> 1. Re: d-link router ssh problems (Chris Bruner)

> ----------------------------------------------------------------------

> Message: 1
> Date: Thu, 30 Jun 2011 00:49:46 -0400
> From: Chris Bruner <cbruner at quadro.net>
> To: KWLUG discussion <kwlug-disc at kwlug.org>
> Subject: Re: [kwlug-disc] d-link router ssh problems
> Message-ID: <4E0C006A.1080006 at quadro.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed

> On 6/28/2011 2:20 PM, Chris Frey wrote:
> > On Tue, Jun 28, 2011 at 01:06:34PM -0400, Chris Bruner wrote:
> >> I'm at quadro which I believes buys internet through bell.
> >> It's not a lot of traffic in my case.
> >> eg. ssh somesite
> >> ls (is ok)
> >> wait 10 minutes
> >> ls (1/2 come to screen connection is broken)
> >>
> >> I'm thinking that it is dlink specific. I'm on the second of 2
> >> routers
> >> with the same problem. Unless traffic shaping started at the same
> >> time
> >> I changed the router, I think it's the router.
> > I remember experiencing something similar a long time ago, with an
> > old
> > Linux box as the router, I think. Unfortunately, I've forgotten the
> > details.
> >
> > Is wireless a part of the equation anywhere? Could there be a
> > frequency
> > interference that didn't happen with the other router?
> It is a wireless router, but the computer where I noticed the error
> is a
> direct connect. Same configuration as the linksys.
> > If you leave something like top running in the window, does it
> > eventually
> > die? If it doesn't die, then it might be a timeout issue. If it
> > does
> > die, then it would seem more fundamental.
> So I left top running on a server that was having problems. No
> problems. Then I let the directory sit for a few hours. still no
> problems.

> The problem has magically gone away...

> > Can you start a long ssh transfer in one direction and see if the
> > time
> > it takes to to die is consistent?
> >
> > cat /dev/zero | ssh host "cat> /dev/null"
> >
> > - Chris
> >
> >
> > _______________________________________________
> > kwlug-disc mailing list
> > kwlug-disc at kwlug.org
> > http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
> >
> >
> >
> >
> > =======
> > Email scanned by PC Tools - No viruses or spyware found.
> > (Email Guard: 7.0.0.18, Virus/Spyware Database: 6.17810)
> > http://www.pctools.com/
> > =======
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kwlug.org/pipermail/kwlug-disc_kwlug.org/attachments/20110630/99bb51de/attachment.htm>