netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Antony Antony <antony@phenome.org>,
	Stephen Hemminger <stephen@networkplumber.org>,
	David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-net v2] ip xfrm: support setting XFRMA_SET_MARK_MASK attribute in states
Date: Tue, 6 Oct 2020 23:11:12 -0700	[thread overview]
Message-ID: <96499050-f8e9-532b-cbd7-f18ba96a651d@gmail.com> (raw)
In-Reply-To: <20201002132238.GA36488@AntonyAntony.local>

On 10/2/20 6:22 AM, Antony Antony wrote:
> The XFRMA_SET_MARK_MASK attribute can be set in states (4.19+)
> It is optional and the kernel default is 0xffffffff
> It is the mask of XFRMA_SET_MARK(a.k.a. XFRMA_OUTPUT_MARK in 4.18)
> 
> e.g.
> ./ip/ip xfrm state add output-mark 0x6 mask 0xab proto esp \
>  auth digest_null 0 enc cipher_null ''
> ip xfrm state
> src 0.0.0.0 dst 0.0.0.0
> 	proto esp spi 0x00000000 reqid 0 mode transport
> 	replay-window 0
> 	output-mark 0x6/0xab
> 	auth-trunc digest_null 0x30 0
> 	enc ecb(cipher_null)
> 	anti-replay context: seq 0x0, oseq 0x0, bitmap 0x00000000
> 	sel src 0.0.0.0/0 dst 0.0.0.0/0
> 
> Signed-off-by: Antony Antony <antony@phenome.org>
> ---
>  v1 -> v2
>   - add man page and usage for mask
> --
>  ip/xfrm_state.c    | 23 ++++++++++++++++++-----
>  man/man8/ip-xfrm.8 |  4 +++-
>  2 files changed, 21 insertions(+), 6 deletions(-)
> 
applied to iproute2-next. Thanks



      reply	other threads:[~2020-10-07  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  4:37 [PATCH iproute2-next] ip xfrm: support setting XFRMA_SET_MARK_MASK attribute in states Antony Antony
2020-10-02 13:22 ` [PATCH iproute2-net v2] " Antony Antony
2020-10-07  6:11   ` David Ahern [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=96499050-f8e9-532b-cbd7-f18ba96a651d@gmail.com \
    --to=dsahern@gmail.com \
    --cc=antony@phenome.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).