From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: netdev@vger.kernel.org, netfilter@vger.kernel.org,
netfilter-announce@lists.netfilter.org, lwn@lwn.net
Subject: [ANNOUNCE] iptables 1.4.14 release
Date: Sat, 26 May 2012 20:15:22 +0200 [thread overview]
Message-ID: <20120526181522.GA32109@1984> (raw)
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Hi!
The Netfilter project proudly presents:
iptables 1.4.14
This release several bugfixes and support for the new cttimeout
infrastructure. This allows you to attach specific timeout policies to
flow via iptables CT target.
The following example shows the usage of this new infrastructure in a
couple of steps:
1) Create a timeout policy with name `custom-tcp-policy1':
nfct timeout add custom-tcp-policy1 inet tcp established 200
2) Attach it to traffic going from 1.1.1.1 to 2.2.2.2
iptables -I PREROUTING -t raw -s 1.1.1.1 -d 2.2.2.2 -p tcp \
-j CT --timeout custom-tcp-policy1
The new nfct resides in the conntrack-tools tree. By now, this new
utility only supports the cttimeout. In the long run, the plan is to
replace the conntrack utility with it.
See ChangeLog that comes attached to this email for more details.
You can download it from:
http://www.netfilter.org/projects/conntrack-tools/downloads.html
ftp://ftp.netfilter.org/pub/conntrack-tools/
Have fun!
[-- Attachment #2: changes-iptables-1.4.14.txt --]
[-- Type: text/plain, Size: 373 bytes --]
Florian Westphal (3):
ip(6)tables-restore: make sure argv is NULL terminated
extensions: libxt_rateest: output all options in save hook
tests: add rateest match rules
Miguel GAIO (1):
libiptc: fix retry path in TC_INIT
Pablo Neira Ayuso (3):
libxt_CT: add --timeout option
libipt_ULOG: fix --ulog-cprange
Bump version to 1.4.14
reply other threads:[~2012-05-26 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120526181522.GA32109@1984 \
--to=pablo@netfilter.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-announce@lists.netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).