All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Mark Gillott <mgillott@vyatta.att-mail.com>, netdev@vger.kernel.org
Cc: steffen.klassert@secunet.com, herbert@gondor.apana.org.au
Subject: Re: [PATCH ipsec] xfrm: check DST_NOPOLICY as well as DST_NOXFRM
Date: Thu, 5 Dec 2019 09:52:21 +0100	[thread overview]
Message-ID: <c050dc8c-eb17-7195-51ed-18de0a270f5b@6wind.com> (raw)
In-Reply-To: <9a0813f2446b0423963d871795e34b3fe99e301d.camel@vyatta.att-mail.com>

Le 05/12/2019 à 09:10, Mark Gillott a écrit :
> On Wed, 2019-12-04 at 17:57 +0100, Nicolas Dichtel wrote:
>> Le 04/12/2019 à 16:17, Mark Gillott a écrit :
>>> Before performing a policy bundle lookup, check the DST_NOPOLICY
>>> option, as well as DST_NOXFRM. That is, skip further processing if
>>> either of the disable_policy or disable_xfrm sysctl attributes are
>>> set.
>>
>> Can you elaborate why this change is needed?
> 
> We have a separate DPDK-based dataplane that is responsible for all
> IPsec processing - policy handing/encryption/decryption. Consequently
> we set the net.ipv[4|6].conf.<if>.disable_policy sysctl to 1 for all
> "interesting" interfaces. That is we want the kernel to ignore any
> IPsec policies.
> 
> Despite the above & depending on configuration, we found that
> originating traffic was ending up deep inside XFRM where it would get
> dropped because of a route lookup problem.
And why don't you set disable_xfrm to thoses interfaces also?
disable_policy means no xfrm policy lookup on output, disable_xfrm means no xfrm
policy check on input.

Nicolas

  reply	other threads:[~2019-12-05  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 15:17 [PATCH ipsec] xfrm: check DST_NOPOLICY as well as DST_NOXFRM Mark Gillott
2019-12-04 16:57 ` Nicolas Dichtel
2019-12-05  8:10   ` Mark Gillott
2019-12-05  8:52     ` Nicolas Dichtel [this message]
2019-12-05 10:05       ` Mark Gillott
2019-12-05 10:51         ` Nicolas Dichtel
2019-12-05 11:11           ` Mark Gillott

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=c050dc8c-eb17-7195-51ed-18de0a270f5b@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=mgillott@vyatta.att-mail.com \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /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.