From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
"'netfilter@vger.kernel.org'" <netfilter@vger.kernel.org>,
netfilter-announce@lists.netfilter.org
Subject: [ANNOUNCE]: Release of iptables-1.4.6
Date: Wed, 09 Dec 2009 15:48:08 +0100 [thread overview]
Message-ID: <4B1FB8A8.10505@trash.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
The netfilter coreteam presents:
iptables version 1.4.6
the iptables release for the 2.6.32 kernel. Changes include:
- manpage updates
- multiple smaller fixes for xt_iprange, xt_conntrack, iptables
rule deletion and replacement, inverted argument parsing
- addition of the xt_osf extension
- code cleanups
See the changelog for more details.
Version 1.4.6 can be obtained from:
http://www.netfilter.org/projects/iptables/downloads.html
ftp://ftp.netfilter.org/pub/iptables/
git://git.netfilter.org/iptables.git
On behalf of the Netfilter Core Team.
Happy firewalling!
[-- Attachment #2: changes-iptables-1.4.6.txt --]
[-- Type: text/plain, Size: 1743 bytes --]
Jan Engelhardt (20):
iptables: manpage updates for augmented -Z syntax
doc: mention maximum mark size in manpages
Support for nommu arches
realm: remove static initializations
libiptc: remove unused functions
libiptc: avoid strict-aliasing warnings
iprange: do accept non-ranges for xt_iprange v1
iprange: warn on reverse range
iprange: roll address parsing into a loop
iprange: do accept non-ranges for xt_iprange v1 (log)
iprange: warn on reverse range (log)
libiptc: fix wrong maptype of base chain counters on restore
iptables: fix undersized deletion mask creation
style: reduce indent in xtables_check_inverse
libxtables: hand argv to xtables_check_inverse
iptables/extensions: make bundled options work again
CONNMARK: print mark rules with mask 0xffffffff as set instead of xset
iptables: take masks into consideration for replace command
doc: explain experienced --hitcount limit
doc: name resolution clarification
Mohit Mehta (1):
iptables: expose option to zero packet/byte counters for a specific rule
Olaf Rempel (1):
build: restore --disable-ipv6 functionality on system w/o v6 headers
Patrick McHardy (7):
Merge branch 'zero' of git://dev.medozas.de/iptables
MARK: print mark rules with mask 0xffffffff as --set-mark instead of --set-xmark
DNAT: fix incorrect check during parsing
extensions: add osf extension
conntrack: fix --expires parsing
Merge branch 'master' of git://dev.medozas.de/iptables
Bump version to v1.4.6
Tim Small (1):
doc: update TCPMSS manpage with Linux 2.6.25 changes
sobtwmxt (1):
doc: fix typo in length manpage
reply other threads:[~2009-12-09 14:48 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=4B1FB8A8.10505@trash.net \
--to=kaber@trash.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).