All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: netfilter-devel@vger.kernel.org
Cc: Florian Westphal <fw@strlen.de>, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [iptables PATCH 0/8] Fix xtables-monitor rule printing, partially RFC
Date: Sat, 27 Jul 2024 14:33:37 +0200	[thread overview]
Message-ID: <ZqTpIS44pyYLTk-p@orbyte.nwl.cc> (raw)
In-Reply-To: <20240716122805.22331-1-phil@nwl.cc>

On Tue, Jul 16, 2024 at 02:27:57PM +0200, Phil Sutter wrote:
> The patches in this series progress from fixes to features, and for the
> last two I'm not sure they are acceptable as-is: Patch 7 is not entirely
> complete, one should follow-up printing ebtables policy rules like
> builtin chain policies in traces but it requires quite some code churn.
> Patch 8 changes output of both events and traces, thus might break
> existing scripts parsing xtables-monitor output.
> 
> Phil Sutter (8):
>   xtables-monitor: Proper re-init for rule's family
>   xtables-monitor: Flush stdout after all lines of output
>   xtables-monitor: Align builtin chain and table output
>   xtables-monitor: Support arptables chain events
>   tests: shell: New xtables-monitor test
>   xtables-monitor: Fix for ebtables rule events
>   xtables-monitor: Ignore ebtables policy rules unless tracing
>   xtables-monitor: Print commands instead of -4/-6/-0 flags

Series applied.

      parent reply	other threads:[~2024-07-27 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 12:27 [iptables PATCH 0/8] Fix xtables-monitor rule printing, partially RFC Phil Sutter
2024-07-16 12:27 ` [iptables PATCH 1/8] xtables-monitor: Proper re-init for rule's family Phil Sutter
2024-07-16 12:27 ` [iptables PATCH 2/8] xtables-monitor: Flush stdout after all lines of output Phil Sutter
2024-07-16 12:28 ` [iptables PATCH 3/8] xtables-monitor: Align builtin chain and table output Phil Sutter
2024-07-16 12:28 ` [iptables PATCH 4/8] xtables-monitor: Support arptables chain events Phil Sutter
2024-07-16 12:28 ` [iptables PATCH 5/8] tests: shell: New xtables-monitor test Phil Sutter
2024-07-16 12:28 ` [iptables PATCH 6/8] xtables-monitor: Fix for ebtables rule events Phil Sutter
2024-07-16 12:28 ` [iptables PATCH 7/8] xtables-monitor: Ignore ebtables policy rules unless tracing Phil Sutter
2024-07-16 12:28 ` [RFC iptables PATCH 8/8] xtables-monitor: Print commands instead of -4/-6/-0 flags Phil Sutter
2024-07-27 12:33 ` Phil Sutter [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=ZqTpIS44pyYLTk-p@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.