[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180611201259.0fc206d0@xeon-e3>
Date: Mon, 11 Jun 2018 20:12:59 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>
Cc: lorenzo@...gle.com, netdev@...r.kernel.org, dsahern@...il.com
Subject: Re: [PATCH iproute2-next] ip-xfrm: Add support for OUTPUT_MARK
On Mon, 11 Jun 2018 20:11:33 -0600
Subash Abhinov Kasiviswanathan <subashab@...eaurora.org> wrote:
> This patch adds support for OUTPUT_MARK in xfrm state to exercise the
> functionality added by kernel commit 077fbac405bf
> ("net: xfrm: support setting an output mark.").
>
> Sample output with output-mark -
>
> src 192.168.1.1 dst 192.168.1.2
> proto esp spi 0x00004321 reqid 0 mode tunnel
> replay-window 0 flag af-unspec
> auth-trunc xcbc(aes) 0x3ed0af408cf5dcbf5d5d9a5fa806b211 96
> enc cbc(aes) 0x3ed0af408cf5dcbf5d5d9a5fa806b233
> anti-replay context: seq 0x0, oseq 0x0, bitmap 0x00000000
> output-mark 0x20000
>
> Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>
This reminds me. It is time to convert xfrm to json output.
Powered by blists - more mailing lists