Message ID | 20221118225043.1361845-1-adolf.belka@ipfire.org |
---|---|
State | Accepted |
Commit | b685b5e7e9e2f6d48cae352431d82f3a96962e3d |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4NDX7q4sKqz3wgd for <patchwork@web04.haj.ipfire.org>; Fri, 18 Nov 2022 22:51:03 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4NDX7n1z4yz2mv; Fri, 18 Nov 2022 22:51:01 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4NDX7n13Mhz2xqt; Fri, 18 Nov 2022 22:51:01 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4NDX7l1nJ8z2xKv for <development@lists.ipfire.org>; Fri, 18 Nov 2022 22:50:59 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4NDX7k3FWkz19J; Fri, 18 Nov 2022 22:50:58 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1668811858; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=XEpkh+yZjwApov/be9bZV4HMRpKTC8m+3W/nLLzBVAc=; b=JPBOJZ1mncXZKfJ8RpNWZFNSHZiILxhwb32YaUQdIT+XPNlHtaqTyIh2d5Pvm3kTYv3GgE z9kuXvk4dsiPTaBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1668811858; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=XEpkh+yZjwApov/be9bZV4HMRpKTC8m+3W/nLLzBVAc=; b=snscSyXd/fvY5qfiHwNjYpIzLDhnxynwhLaB6G4mvEfHmEDwN/TZEDJuKG1qmbi1gKgaWy zSZNpre+PZcjN0/HqP4os5FEylKmjjdO6aHw3F1YuXyBnZZR8pA8vnGytCNv8sW405unUp 3A5tfE+tgAH85zKmtDTLwnQCMjzEwzWxl2C7WfVwq2upZHWrNlJFZWRjE/7xtVuDECD9h8 lH6ilEC6/sOIb2Z10OuDV90e+DGRt79B2955uSeikdp+CDXacnudVDIZ5PK2LPtYjXMlnS Z33YoFbvuQ1EqA2FL2eQvO/67PiFgvsXHMCrkYCdbGxTJI/xUQcuTcUVUSOlNA== From: Adolf Belka <adolf.belka@ipfire.org> To: development@lists.ipfire.org Subject: [PATCH 1/2] conntrack-tools: Update to version 1.4.7 Date: Fri, 18 Nov 2022 23:50:42 +0100 Message-Id: <20221118225043.1361845-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <https://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <https://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Series |
[1/2] conntrack-tools: Update to version 1.4.7
|
|
Commit Message
Adolf Belka
Nov. 18, 2022, 10:50 p.m. UTC
- Update from 1.4.6 to 1.4.7
- Update of rootfile not required
- Requires update fo libnetfilter_conntrack from 1.0.8 to 1.0.9
- Changelog
conntrack-tools 1.4.7
This release contains new features:
* IPS_HW_OFFLOAD flag specifies that a conntrack entry has been
offloaded into the hardware
* 'clash_resolve' and 'chaintoolong' stats counters
* Default to unspec family if '-f' flag is absent to improve support for
dual-stack setups
* Support filtering events by IP address family
* Support flushing per IP address family
* Add "save" output format representing data in conntrack parameters
* Support loading conntrack commands from a batch file, e.g. generated
by "save" output format
* Annotate portid in events by the program name (if found)
* Accept yes/no as synonyms to on/off in conntrackd.conf
* Support user space helper auto-loading upon daemon startup, relieving
users from manual 'nfct add helper' calls
* Filter dumps by status on kernel side if possible
* Accept to filter for any status other than SEEN_REPLY using
'UNREPLIED'
* Use libmnl internally
* Reuse netlink socket for improved performance with bulk CT entry loads
* Remove '-o userspace' flag and always tag user space triggered events
* Introduce '-A' command, a variant of '-I' which does not fail if the
entry exists already
... and fixes:
* ICMP entry creation would fail when reply data was specified
* Sync zone value also
* Log external inject problems as warning only
* Endianness bug parsing IP addresses
* Ignore conntrack ID when looking up cache entries to allow for stuck
old ones to be replaced eventually
* Broken parsing of IPv6 M-SEARCH requests in ssdp cthelper
* Eliminate the need for lazy binding in nfct
* Fix for use of unknown protocol values
* Sanitize protocol value parsing, catch illegal values
* Ensure unknown protocol values are included in '-o save' dumps
... and documentation updates:
* Fixed examples in manual
* Refer to nf_conntrack sysctl instead of the deprecated ip_conntrack
one
* Misc updates to the manual
* Add an older example script creating an active-active setup using the
cluster match
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/conntrack-tools | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
Reviewed-by: Michael Tremer <michael.tremer@ipfire.org> > On 18 Nov 2022, at 22:50, Adolf Belka <adolf.belka@ipfire.org> wrote: > > - Update from 1.4.6 to 1.4.7 > - Update of rootfile not required > - Requires update fo libnetfilter_conntrack from 1.0.8 to 1.0.9 > - Changelog > conntrack-tools 1.4.7 > This release contains new features: > * IPS_HW_OFFLOAD flag specifies that a conntrack entry has been > offloaded into the hardware > * 'clash_resolve' and 'chaintoolong' stats counters > * Default to unspec family if '-f' flag is absent to improve support for > dual-stack setups > * Support filtering events by IP address family > * Support flushing per IP address family > * Add "save" output format representing data in conntrack parameters > * Support loading conntrack commands from a batch file, e.g. generated > by "save" output format > * Annotate portid in events by the program name (if found) > * Accept yes/no as synonyms to on/off in conntrackd.conf > * Support user space helper auto-loading upon daemon startup, relieving > users from manual 'nfct add helper' calls > * Filter dumps by status on kernel side if possible > * Accept to filter for any status other than SEEN_REPLY using > 'UNREPLIED' > * Use libmnl internally > * Reuse netlink socket for improved performance with bulk CT entry loads > * Remove '-o userspace' flag and always tag user space triggered events > * Introduce '-A' command, a variant of '-I' which does not fail if the > entry exists already > ... and fixes: > * ICMP entry creation would fail when reply data was specified > * Sync zone value also > * Log external inject problems as warning only > * Endianness bug parsing IP addresses > * Ignore conntrack ID when looking up cache entries to allow for stuck > old ones to be replaced eventually > * Broken parsing of IPv6 M-SEARCH requests in ssdp cthelper > * Eliminate the need for lazy binding in nfct > * Fix for use of unknown protocol values > * Sanitize protocol value parsing, catch illegal values > * Ensure unknown protocol values are included in '-o save' dumps > ... and documentation updates: > * Fixed examples in manual > * Refer to nf_conntrack sysctl instead of the deprecated ip_conntrack > one > * Misc updates to the manual > * Add an older example script creating an active-active setup using the > cluster match > > Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> > --- > lfs/conntrack-tools | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/lfs/conntrack-tools b/lfs/conntrack-tools > index 7bfd71d89..2296c7ca8 100644 > --- a/lfs/conntrack-tools > +++ b/lfs/conntrack-tools > @@ -24,7 +24,7 @@ > > include Config > > -VER = 1.4.6 > +VER = 1.4.7 > > THISAPP = conntrack-tools-$(VER) > DL_FILE = $(THISAPP).tar.bz2 > @@ -42,7 +42,7 @@ objects = $(DL_FILE) > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE) > > -$(DL_FILE)_BLAKE2 = 7c1ee1c5fc2b6f9d33c6cf850eca80978b8763317b1a76892cefb776130564f15fbd4e4554fdb08dbba93d9f16b7e4624a1b4dd5a631f747f5fcc0a5b01b8d5e > +$(DL_FILE)_BLAKE2 = 42a3cacf8a32a5b8b688a9fd68f66024c591e9814ef3cc349456691094bab0fae15bb1c00befa178b0f8e845bf6fc00715cbf9db55cd7bf2d155c2dfd55f9b1a > > install : $(TARGET) > > -- > 2.38.1 >
diff --git a/lfs/conntrack-tools b/lfs/conntrack-tools index 7bfd71d89..2296c7ca8 100644 --- a/lfs/conntrack-tools +++ b/lfs/conntrack-tools @@ -24,7 +24,7 @@ include Config -VER = 1.4.6 +VER = 1.4.7 THISAPP = conntrack-tools-$(VER) DL_FILE = $(THISAPP).tar.bz2 @@ -42,7 +42,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 7c1ee1c5fc2b6f9d33c6cf850eca80978b8763317b1a76892cefb776130564f15fbd4e4554fdb08dbba93d9f16b7e4624a1b4dd5a631f747f5fcc0a5b01b8d5e +$(DL_FILE)_BLAKE2 = 42a3cacf8a32a5b8b688a9fd68f66024c591e9814ef3cc349456691094bab0fae15bb1c00befa178b0f8e845bf6fc00715cbf9db55cd7bf2d155c2dfd55f9b1a install : $(TARGET)