From: Jes Sorensen <jes@linuxcare.com>
To: Markus Germeier <mager@tzi.de>
Cc: "David S. Miller" <davem@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.2.19pre9 (Connection closed.)
Date: 22 Feb 2001 14:22:19 +0100 [thread overview]
Message-ID: <d3y9uyj1is.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <94ae7g9o8t.fsf@religion.informatik.uni-bremen.de> <E14VZCs-00023R-00@the-village.bc.nu> <14996.14604.348038.42765@pizda.ninka.net> <948zmy97zc.fsf@religion.informatik.uni-bremen.de>
In-Reply-To: Markus Germeier's message of "22 Feb 2001 14:12:55 +0100"
>>>>> "Markus" == Markus Germeier <mager@tzi.de> writes:
Markus> Tell me if I can provide you with further data to nail down
Markus> this bug.
Alan forwarded a patch to me from DaveM which fixed it for me.
Markus> Jes: I thought about your information that ssh connections do
Markus> not show this problem. I believe you are using ssh 2.3 or 2.4
Markus> from ssh.com, right? 2.3 introduced a rekeying-feature which
Markus> exchanges new keys every 60 minutes, so the TCP keepalive is
Markus> never triggered. (Due to a bug which is still present in 2.4,
Markus> we can't use these versions at my site.)
No way, I don't use software from those slimeballs, I use OpenSSH.
The problems I were seeing were much more than every 2 hrs, more like
every 10-15 mins. Anyway it seems it got fixed.
Jes
next prev parent reply other threads:[~2001-02-22 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 13:09 Problem with 2.2.19pre9 (Connection closed.) Markus Germeier
2001-02-21 13:21 ` Alan Cox
2001-02-21 13:32 ` Jes Sorensen
2001-02-21 13:55 ` Markus Germeier
2001-02-21 15:48 ` Jes Sorensen
2001-02-21 21:54 ` David S. Miller
2001-02-22 13:12 ` Markus Germeier
2001-02-22 13:22 ` Jes Sorensen [this message]
2001-02-22 18:52 ` Henrique de Moraes Holschuh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3y9uyj1is.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mager@tzi.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.