public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] conntrack-tools: Update to version 1.4.7
Date: Sat, 19 Nov 2022 11:52:14 +0000	[thread overview]
Message-ID: <C8863A3D-A8BC-4E10-8BE0-EE616A5BBBE5@ipfire.org> (raw)
In-Reply-To: <20221118225043.1361845-1-adolf.belka@ipfire.org>

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

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 18 Nov 2022, at 22:50, Adolf Belka <adolf.belka(a)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(a)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
> 


      parent reply	other threads:[~2022-11-19 11:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 22:50 Adolf Belka
2022-11-18 22:50 ` [PATCH 2/2] libnetfilter_conntrack: Update to version 1.0.9 Adolf Belka
2022-11-19 11:51   ` Michael Tremer
2022-11-19 11:52 ` Michael Tremer [this message]

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=C8863A3D-A8BC-4E10-8BE0-EE616A5BBBE5@ipfire.org \
    --to=michael.tremer@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