[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2y18242oz.fsf@ja.int.chopps.org>
Date: Wed, 22 May 2024 05:26:13 -0400
From: Christian Hopps <chopps@...pps.org>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Antony Antony <antony.antony@...unet.com>, David Ahern
<dsahern@...il.com>, netdev@...r.kernel.org, devel@...ux-ipsec.org,
Steffen Klassert <steffen.klassert@...unet.com>, Eyal Birger
<eyal.birger@...il.com>, Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Sabrina Dubroca <sd@...asysnail.net>, Christian Hopps <chopps@...pps.org>
Subject: Re: [PATCH RFC iproute2-next 2/3] xfrm: support xfrm SA direction
attribute
Stephen Hemminger <stephen@...workplumber.org> writes:
> On Sun, 19 May 2024 20:37:23 +0200
> Antony Antony <antony.antony@...unet.com> wrote:
>
>> + if (tb[XFRMA_SA_DIR]) {
>> + __u8 dir = rta_getattr_u8(tb[XFRMA_SA_DIR]);
>> +
>> + fprintf(fp, "\tdir ");
>> + if (dir == XFRM_SA_DIR_IN)
>> + fprintf(fp, "in");
>> + else if (dir == XFRM_SA_DIR_OUT)
>> + fprintf(fp, "out");
>> + else
>> + fprintf(fp, " %d", dir);
>> + fprintf(fp, "%s", _SL_);
>> + }
>
> JSON output support please
I would think this should be a different patchset since it would be totally new for iproute xfrm, right?
Thanks,
Chris.
Download attachment "signature.asc" of type "application/pgp-signature" (858 bytes)
Powered by blists - more mailing lists