From: Stephen Jones <hivemynd@hivemynd.net>
To: netfilter@lists.netfilter.org
Subject: Tuning NAT timeout values
Date: Thu, 23 Feb 2006 14:05:29 -0600 [thread overview]
Message-ID: <43FE1589.10205@hivemynd.net> (raw)
In-Reply-To: <43EA2AA5.3080401@arcoscom.com>
Hello all,
I have run into a wall on this one. I have need to change the default
settings on NAT entries through a Linux 2.4.32/iptables 1.2.11 based
firewall. Multiple searches have lead me to believe that tuning NAT
masquerade timeouts through iptables is not possible as it apparently
was through ipchains/ipfwadm.
This document (and other similar linux NAT/MASQ howtos):
http://howtos.linux.com/guides/nag2/x-087-2-masq.configuration.shtml
State: "The iptables implementation uses much longer default timers and
does not allow you to set them." Or something meaning the same thing.
An old discussion about this:
http://www.cs.washington.edu/homes/bdferris/afs_conntrack_nat/index.html
leads me to believe that perhaps if this is possible, it will be through
tuning the various core conntrack tcp/udp settings for the timeouts
(e.g. ip_conntrack_udp_timeout_stream
ip_conntrack_tcp_timeout_close_wait
ip_conntrack_udp_timeout
ip_conntrack_tcp_timeout_close
ip_conntrack_tcp_timeout_time_wait
ip_conntrack_tcp_timeout_syn_sent
ip_conntrack_icmp_timeout
ip_conntrack_tcp_timeout_syn_recv
ip_conntrack_generic_timeout
ip_conntrack_tcp_timeout_last_ack
ip_conntrack_tcp_timeout_fin_wait
ip_conntrack_tcp_timeout_established)
Any guidance on this issue would be greatly appreciated!
SJ
next prev parent reply other threads:[~2006-02-23 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 17:30 Last patch-o-matic patches status report Samuel Díaz García
2006-02-23 20:05 ` Stephen Jones [this message]
2006-02-26 11:56 ` Tuning NAT timeout values ludi
2006-02-26 19:29 ` Stephen Jones
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=43FE1589.10205@hivemynd.net \
--to=hivemynd@hivemynd.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox