From: Erik Skultety <eskultet@redhat.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH] iptables: xshared: Ouptut '--' in the opt field in ipv6's fake mode
Date: Wed, 20 Jul 2022 18:56:00 +0200 [thread overview]
Message-ID: <YtgzoIJngb5edrmu@nautilus.home.lan> (raw)
In-Reply-To: <784718-9pp7-o170-or1q-rnns2802nqs@vanv.qr>
On Wed, Jul 20, 2022 at 06:07:34PM +0200, Jan Engelhardt wrote:
>
> On Wednesday 2022-07-20 15:06, Erik Skultety wrote:
>
> >The fact that the 'opt' table field reports spaces instead of '--' for
> >IPv6 as it would have been the case with IPv4 has a bit of an
> >unfortunate side effect that it completely confuses the 'jc' JSON
> >formatter tool (which has an iptables formatter module).
> >Consider:
> > # ip6tables -L test
> > Chain test (0 references)
> > target prot opt source destination
> > ACCEPT all a:b:c:: anywhere MAC01:02:03:04:05:06
> >
> >Then:
> > # ip6tables -L test | jc --iptables
> > [{"chain":"test",
> > "rules":[
> > {"target":"ACCEPT",
> > "prot":"all",
> > "opt":"a:b:c::",
> > "source":"anywhere",
> > "destination":"MAC01:02:03:04:05:06"
> > }]
> > }]
> >
> >which as you can see is wrong simply because whitespaces are considered
> >as a column delimiter.
>
> Even if you beautify the opt column with a dash, you still have
> problems elsewhere. "MAC01" for example is not the destination
> at all.
That's incorrect - this is what it would look like after this patch:
[{"chain":"test",
"rules":[
{"target":"ACCEPT",
"prot":"all",
"opt": ,
"source": "a:b:c::",
"destination":"anywhere",
"options":"MAC01:02:03:04:05:06"
}]
}]
which actually makes more sense.
I may have not been completely clear about it. With the column "beautifying" we
could keep the current shape of tests, i.e. not trying to use 'jc' to get a JSON
output and instead it would give me time to try address the nature of the checks
in the test suite with nft's native JSON formatter instead which is IMO a more
future-proof design of these old tests.
>
> If you or jc is to parse anything, it must only be done with the
> iptables -S output form.
>
Well, that would be a problem because 'jc' iptables plugin doesn't understand
the -S output (isn't -S considered deprecated or I'm just halucinating?).
Erik
next prev parent reply other threads:[~2022-07-20 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 13:06 [iptables PATCH] iptables: xshared: Ouptut '--' in the opt field in ipv6's fake mode Erik Skultety
2022-07-20 14:20 ` Florian Westphal
2022-07-20 16:11 ` Erik Skultety
2022-07-23 9:47 ` Phil Sutter
2022-07-23 12:35 ` Florian Westphal
2022-07-20 16:07 ` Jan Engelhardt
2022-07-20 16:56 ` Erik Skultety [this message]
2022-07-21 7:22 ` Jan Engelhardt
2022-07-25 21:39 ` Florian Westphal
2022-07-26 6:55 ` Erik Skultety
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=YtgzoIJngb5edrmu@nautilus.home.lan \
--to=eskultet@redhat.com \
--cc=jengelh@inai.de \
--cc=netfilter-devel@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).