From: Phil Sutter <phil@netfilter.org>
To: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Cc: netdev@vger.kernel.org, netfilter-announce@lists.netfilter.org,
lwn@lwn.net
Subject: [ANNOUNCE] iptables 1.8.7 release
Date: Fri, 15 Jan 2021 23:28:57 +0100 [thread overview]
Message-ID: <20210115222857.GA18001@orbyte.nwl.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]
Hi!
The Netfilter project proudly presents:
iptables 1.8.7
This release contains the following fixes and enhancements:
iptables-nft:
- Improved performance when matching on IP/MAC address prefixes if the
prefix is byte-aligned. In ideal cases, this doubles packet processing
performance.
*NOTE*: Older iptables versions will not recognize the mask and thus
omit them when listing the ruleset.
- Dump user-defined chains in lexical order. This way ruleset dumps
become stable and easily comparable.
- Avoid pointless table/chain creation. For instance, 'iptables-nft -L'
no longer creates missing base-chains.
ebtables-nft:
- Renaming user-defined chains was entirely broken.
extensions:
- Code for printing and parsing of MAC addresses was consolidated
internally, slightly reducing binary size. As a noticeable
side-effect, all MAC addresses are now printed in lower-case (affects
'mac'-extension).
- Fixed DCCP extension's match on 'INVALID' type, a meta-type which
should match any type value in the range from ten to fifteen. In the
past it matched on type value 10 only.
xtables-monitor:
- Don't print unrelated rules in the same chain when tracing.
- Flush output buffer after each rule when tracing to improve experience
when redirecting output.
- Print the table's family when tracing instead of whatever the user
specified on command line.
- Print the traced packet before the rule it traverses, not vice-versa.
- Recognize loopback interface and print "LOOPBACK" for link layer
header info instead of "LL=0x304".
xtables-translate:
- Correctly translate DCCP type matches (including 'INVALID').
See the attached changelog for more details.
You can download it from:
http://www.netfilter.org/projects/iptables/downloads.html#iptables-1.8.7
To build the code, libnftnl 1.1.6 is required:
* http://netfilter.org/projects/libnftnl/downloads.html#libnftnl-1.1.6
In case of bugs and feature requests, file them via:
* https://bugzilla.netfilter.org
Happy firewalling!
[-- Attachment #2: iptables-1.8.7.txt --]
[-- Type: text/plain, Size: 1311 bytes --]
Florian Westphal (4):
xtables-monitor: fix rule printing
xtables-monitor: fix packet family protocol
xtables-monitor: print packet first
xtables-monitor: 'LL=0x304' is not very convenient, print LOOPBACK instead.
Pablo Neira Ayuso (1):
tests: shell: update format of registers in bitwise payloads.
Phil Sutter (21):
nft: Optimize class-based IP prefix matches
ebtables: Optimize masked MAC address matches
tests/shell: Add test for bitwise avoidance fixes
ebtables: Fix for broken chain renaming
iptables-test.py: Accept multiple test files on commandline
iptables-test.py: Try to unshare netns by default
libxtables: Extend MAC address printing/parsing support
xtables-arp: Don't use ARPT_INV_*
xshared: Merge some command option-related code
tests/shell: Test for fixed extension registration
extensions: dccp: Fix for DCCP type 'INVALID'
nft: Fix selective chain compatibility checks
nft: cache: Introduce nft_cache_add_chain()
nft: Implement nft_chain_foreach()
nft: cache: Move nft_chain_find() over
nft: Introduce struct nft_chain
nft: Introduce a dedicated base chain array
nft: cache: Sort custom chains by name
tests: shell: Drop any dump sorting in place
nft: Avoid pointless table/chain creation
tests/shell: Fix nft-only/0009-needless-bitwise_0
reply other threads:[~2021-01-15 22:29 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=20210115222857.GA18001@orbyte.nwl.cc \
--to=phil@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).