public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] iptables: Update to version 1.8.7
Date: Thu, 21 Jan 2021 21:17:06 +0100	[thread overview]
Message-ID: <20210121201706.2076325-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2760 bytes --]

- Update from 1.8.6 to 1.8.7
Florian Westphal (4):
      xtables-monitor: fix rule printing
      xtables-monitor: fix packet family protocol
      xtables-monitor: print packet first
      xtables-monitor:

Pablo Neira Ayuso (2):
      tests: shell: update format of registers in bitwise payloads.
      configure: bump version for 1.8.7 release

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
- Rootfile updated

Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
 config/rootfiles/common/iptables | 2 +-
 lfs/iptables                     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/config/rootfiles/common/iptables b/config/rootfiles/common/iptables
index 564578216..b8bf748a5 100644
--- a/config/rootfiles/common/iptables
+++ b/config/rootfiles/common/iptables
@@ -13,7 +13,7 @@ lib/libipq.so.0.0.0
 #lib/libxtables.la
 lib/libxtables.so
 lib/libxtables.so.12
-lib/libxtables.so.12.3.0
+lib/libxtables.so.12.4.0
 #lib/xtables
 lib/xtables/libip6t_DNAT.so
 lib/xtables/libip6t_DNPT.so
diff --git a/lfs/iptables b/lfs/iptables
index 852cde6cc..7b0d0b637 100644
--- a/lfs/iptables
+++ b/lfs/iptables
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 1.8.6
+VER        = 1.8.7
 
 THISAPP    = iptables-$(VER)
 DL_FILE    = $(THISAPP).tar.bz2
@@ -41,7 +41,7 @@ objects = $(DL_FILE) \
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 netfilter-layer7-v2.23.tar.gz = $(URL_IPFIRE)/netfilter-layer7-v2.23.tar.gz
 
-$(DL_FILE)_MD5 = bc0f0adccc93c09dc5b7507ccba93148
+$(DL_FILE)_MD5 = 602ba7e937c72fbb7b1c2b71c3b0004b
 netfilter-layer7-v2.23.tar.gz_MD5 = 10910b6173d18e426cb56ae7e1300eeb
 
 install : $(TARGET)
-- 
2.30.0


             reply	other threads:[~2021-01-21 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 20:17 Adolf Belka [this message]
2021-01-22 22:27 ` Peter Müller
2021-01-25 21:24   ` Michael Tremer

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=20210121201706.2076325-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.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