On 7/27/07, Ralph Shumaker <[EMAIL PROTECTED]> wrote:
>
> Earlier today, while I was sitting at my computer, Pidgin threw up an
> error dialog telling me that the connection had been reset by peer. I
> don't know what that means. But what got my attention is that I had to
> do a few clicks to reconnect. So something must not be set for
> automatic reconnect.
Not sure. But here below is a solution to a similar "connection reset
by peer" problem. In my case, it was related to ssh.
>
> > On 5/18/06, kelsey hudson <[EMAIL PROTECTED]> wrote:
> > > Carl Lowenstein wrote:
> > > > Frequently I log in by ssh to a remote computer. If I don't keep
> > > > using the connection, after a few minutes I get the message
> > > > " Read from remote host deeptow: Connection reset by peer
> > > > Connection to deeptow closed."
> > >
> >
> > > TCPKeepAlive yes
> > > ServerAliveInterval 30
> > > ServerAliveCountMax 3
> > >
> > > That way it pings the server every 30 seconds. If, after a minute and a
> > > half, the machine doesn't respond, the connection is dropped. This also
> > > has the benefit of keeping translation entries open.
> > >
> >
> > This seems to have cured the problem. The next question is: why are
> > these ssh configuration parameters not mentioned in ssh_config(5) or
> > in /etc/ssh/ssh_config? Maybe there is other documentation for ssh.
> > (OpenSSH)?
> One more followup. After reviewing the documentation, and trying some
> experiments, the only modification needed to /etc/ssh/ssh_config is:
> ServerAliveInterval 30
> TCPKeepAlive is deprecated, and seems not to be necessary.
> ServerAliveCountMax 3 is the default value.
For what it's worth this has kept my ssh connections up for weeks at a
time. Your problem with pidgin may be completely different.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
