From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "mael.boutin" <mael.boutin@laposte.net>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>,
netfilter@lists.netfilter.org
Subject: Re: Conntrack timeout
Date: Thu, 09 Nov 2006 15:51:43 +0100 [thread overview]
Message-ID: <4553407F.1060707@netfilter.org> (raw)
In-Reply-To: <J8GVB6$58359DC0230295AB48BF9CF1D57F3A80@laposte.net>
Hi,
I've cc'ed this email to netfilter users mailling list since I think
that this question is not so related with the development.
mael.boutin wrote:
> I wanted to know if it is possible to change the default
> timeout for conntrack entries. And if a modification of these
> timeout will not have border effects on other system features.
You can change them via:
- /proc/sys/net/ipv4/netfilter/ip_conntrack_[tcp|udp]_*
- conntrack tool/libnetfilter_conntrack library
What do you mean with border effects? Of course the behaviour will
change, think about halted TCP connections for whatever reason, if the
timeout is higher then they will get stuck longer in the conntrack table.
> I noticed for example that the UDP timeout is set to 30
> seconds if the connection is not assured and 180 in the other
> case.
>
> The problem i am facing is that i want to detect the end of a
> connection as soon as possible and a delay of 1 or 2 minutes
> is clearly not acceptable.
>
> I found some conf files in /proc/sys/net/netfilter, however
> not all the timeouts are represented
Which timers are you referring to?
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2006-11-09 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 14:09 Conntrack timeout mael.boutin
2006-11-09 14:51 ` Pablo Neira Ayuso [this message]
[not found] <J8GZ11$7A6D86EA0A1A0E5E6A1868598F117CEE@laposte.net>
2006-11-10 0:37 ` Pablo Neira Ayuso
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=4553407F.1060707@netfilter.org \
--to=pablo@netfilter.org \
--cc=mael.boutin@laposte.net \
--cc=netfilter-devel@lists.netfilter.org \
--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.