All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheldon Hearn <sheldonh@starjuice.net>
To: Real Cucumber <monkcucumber@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: SSH Connections Lost After 1 minute idle
Date: Wed, 14 Jul 2004 13:42:20 +0200	[thread overview]
Message-ID: <1089805340.19080.21.camel@axl.seasidesoftware.co.za> (raw)
In-Reply-To: <20040713165106.65338.qmail@web40710.mail.yahoo.com>

On Tue, 2004-07-13 at 18:51, Real Cucumber wrote:
> I have a fedora firewall/router using iptables to
> forward incoming SSH packets to an internal server and
> it works great....however, only if the user does not
> remain idle for 1 minute.

If you're going to use SSH through a stateful firewall, you should
disable out-of-band keep-alives and enable in-connection keep-alives.

I use this in sshd_config:

# In older versions of OpenSSH, it's KeepAlive, not TCPKeepAlive
TCPKeepAlive no
ClientAliveInterval 30
ClientAliveCountMax 120

See the sshd_config(5) manual page for implications.

Ciao,
Sheldon.



  parent reply	other threads:[~2004-07-14 11:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 16:51 SSH Connections Lost After 1 minute idle Real Cucumber
2004-07-13 18:01 ` Antony Stone
2004-07-13 20:57   ` Real Cucumber
2004-07-13 21:18     ` Antony Stone
2004-07-13 21:55       ` Dick St.Peters
2004-07-13 22:06         ` Antony Stone
2004-07-13 22:25         ` Real Cucumber
2004-07-13 22:35           ` Antony Stone
2004-07-13 22:48             ` Real Cucumber
2004-07-13 23:11               ` Antony Stone
2004-07-14 11:42 ` Sheldon Hearn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-13 22:28 Hudson Delbert J Contr 61 CS/SCBN
2004-07-13 22:58 ` Antony Stone
2004-07-13 23:29 Jason Opperisano
2004-07-14  3:48 ` George Alexandru Dragoi
2004-07-14 13:31 ` P
     [not found] <Pine.GSU.4.58.0407131830460.14186@adore.lightlink.com>
2004-07-13 23:32 ` Real Cucumber
2004-07-13 23:49   ` Antony Stone

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=1089805340.19080.21.camel@axl.seasidesoftware.co.za \
    --to=sheldonh@starjuice.net \
    --cc=monkcucumber@yahoo.com \
    --cc=netfilter@lists.netfilter.org \
    /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.