All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: SSH Connections Lost After 1 minute idle
Date: Tue, 13 Jul 2004 19:01:21 +0100	[thread overview]
Message-ID: <200407131901.21907.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040713165106.65338.qmail@web40710.mail.yahoo.com>

On Tuesday 13 July 2004 5:51 pm, 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 they idle for 1 minute,
> the connection "freezes"
>
> If the user is connecting from within the network,
> they can remain idle for an unlimited amount of time
> without being disconnected.  It is only ones
> connecting from outside hte network going through the
> iptables firewall that have this idle problem.
>
> I am only allowing TCP and UDP for SSH to be
> forwarded.

I assume you mean TCP for SSH and TCP/UDP for DNS?   (You don't need UDP for 
SSH...)

> Do I need any ICMP or any other special connection
> timeout rules on the iptables side to fix this problem?

You should not completely block ICMP, although I regard that as a side issue 
and not necessarily the cause of your problem.

It sounds like an ARP cache timeout problem to me.

Try the following test:

1. Connect from an external client to the internal SSH server.
2. Log in on the console of the SSH server (ie: not using the SSH connection) 
and start a ping to the firewall (I don't care whether it gets replies or 
not).
3. Type some command on the SSH client and check you get a response.
4. Wait >1 minute and then type another command on the SSH client and check 
you still get a response.
5. Cancel the ping test from the SSH server to the firewall.
6. Wait >1 minute and then type another command on the SSH client and see if 
the connection has died.

If the above confirms that during a ping, the connection is maintained, and in 
the absence of a ping, the connection dies, then it strongly suggests that 
the firewall is losing the MAC address of the SSH server after a period of no 
activity (or perhaps the SSH server loses the MAC address of the Firewall - 
check both arp caches with "arp -an" on each machine to find out).

It might help to post your ruleset so we can comment on anything we see that 
might cause this problem.

Regards,

Antony.

-- 
Microsoft may sell more software than any other company, but McDonald's sell 
more burgers than any other company, and I think the other similarities are 
obvious...

                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-07-13 18:01 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 [this message]
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
  -- 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=200407131901.21907.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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.