From: Lee Revell <rlrevell@joe-job.com>
To: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ip contrack problem, not strictly followed RFC, DoS very much possible
Date: Mon, 06 Dec 2004 14:31:45 -0500 [thread overview]
Message-ID: <1102361505.2897.25.camel@krustophenia.net> (raw)
In-Reply-To: <20041206191107.GA7192@localhost>
On Mon, 2004-12-06 at 20:11 +0100, Jose Luis Domingo Lopez wrote:
> It is not unusual the need to tweak the settings for several commercial
> firewalls I work with in several customers to raise the default timeouts
> for TCP connection tracking, because some application breaks if the
> connection gets put out of the firewalls' connection tables and the
> traffic dropped.
>
> Many times is just "my users are too lazy to double click the 'start
> connection' icon again when they come from their breakfast, and want to be
> able to enter commands on the remote host again". But at least, the
> parameter is tunable in recent kernel versions, and not hardcoded in the
> kernel sources like it was some time ago.
This is not an application problem. TCP is a reliable, connection
oriented protocol. Users are right to expect that their TCP connections
do not get timed out by an overzealous firewall because the user did not
type anything in an SSH window for 20 minutes.
The problem here is that your firewall is too dumb or your firewall
rules too aggressive to distinguish a valid connection from a security
threat. Please don't blame the users.
Lee
next prev parent reply other threads:[~2004-12-06 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 13:54 ip contrack problem, not strictly followed RFC, DoS very much possible Grzegorz Piotr Jaskiewicz
2004-12-06 14:28 ` Baruch Even
2004-12-06 19:11 ` Jose Luis Domingo Lopez
2004-12-06 19:31 ` Lee Revell [this message]
2004-12-06 19:48 ` Valdis.Kletnieks
2004-12-06 22:20 ` gj
2004-12-06 22:48 ` Willy Tarreau
2004-12-07 8:56 ` [netfilter-core] " Jozsef Kadlecsik
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=1102361505.2897.25.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@24x7linux.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox