From: Andrey Repin <anrdaemon@yandex.ru>
To: "Frances B. Webb" <frances.webb@cornell.edu>, cygwin@cygwin.com
Subject: Re: trouble maintaining an open ssh connection past 20 minutes
Date: Fri, 5 Jun 2020 22:05:34 +0300 [thread overview]
Message-ID: <366236392.20200605220534@yandex.ru> (raw)
In-Reply-To: <CH2PR04MB66968E9DE9B05D14E7DD291887860@CH2PR04MB6696.namprd04.prod.outlook.com>
Greetings, Frances B. Webb!
> My ssh config is this, followed by a bunch of hostname aliases:
> Host *
> ServerAliveInterval 180
> Host solr* jenkins folio*
> IdentityFile ~/.ssh/aws_id_rsa
> The ServerAliveInterval is something I added when I was trying to debug the
> issue last summer. It didn't work, and I never took it out.
I hope you are aware that all matching operators mutually exclusive?
> The servers that I'm communicating with are a combination of Amazon Web
> Services hosted and on-campus server farm machines. Both sets are virtual
> machines, if that makes any difference. I did ask last summer, and all I got
> from our operations people was an assurance that they definitely didn't set
> up the servers to limit ssh sessions to 20 minutes. If there are specific
> misconfigurations that someone can suggest I check or ask them about, I'd be
> happy to pursue that further. Out-of-date server software is worth looking
> into if there are known incompatibilities.
Do you have any local firewall software installed?
--
With best regards,
Andrey Repin
Friday, June 5, 2020 22:04:09
Sorry for my terrible english...
next prev parent reply other threads:[~2020-06-05 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 15:05 Frances B. Webb
[not found] ` <1500186340.2276600.1591369926471@mail.yahoo.com>
2020-06-05 15:26 ` Frances B. Webb
2020-06-05 19:05 ` Andrey Repin [this message]
2020-06-05 20:27 ` Kevin Schnitzius
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=366236392.20200605220534@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=frances.webb@cornell.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).