diff options
| author |   Neale Ranns <nranns@cisco.com> | 2020-10-07 13:58:56 +0000 |
|---|---|---|
| committer |   Damjan Marion <dmarion@me.com> | 2020-10-08 06:20:47 +0000 |
| commit | 970187bd969631da3e81d9bb1691ab88a997f79e (patch) | |
| tree | af2f97c88098f06444434c2678196d9b4f36875c /src | |
| parent | 21fb4f71ee3824c8f177045f21fea258ece602a9 (diff) | |
ipsec: Allow SAs with NULL auth &crypto on IPSec interface
Type: improvement
on the dedicated IPSec interface, the SA describes the peer, so it is
not possible to forward to a peer for which there is no SA. Therefore if
an SA is added with NULL auth and integ then this explicitly states that
this is what the peer desires.
on the contrary on the IP-IP/GRE interface, in the absence of protection
and an SA, then the traffic is sent in the clear. So adding NULL
auth/crypto iSA is a means to describe that the peer should not be sent
traffic.
Signed-off-by: Neale Ranns <nranns@cisco.com>
Change-Id: I7ad2d466cc74eb7ff8c4c84e0d7897d06e2fcf86
Diffstat (limited to 'src')
| -rw-r--r-- | src/vnet/ipsec/ipsec_tun.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/vnet/ipsec/ipsec_tun.c b/src/vnet/ipsec/ipsec_tun.c index e2e1a3e405b..4a84201210e 100644 --- a/src/vnet/ipsec/ipsec_tun.c +++ b/src/vnet/ipsec/ipsec_tun.c @@ -147,8 +147,9 @@ ipsec_tun_protect_get_adj_next (vnet_link_t linkt, sa = ipsec_sa_get (itp->itp_out_sa); im = &ipsec_main; - if (sa->crypto_alg == IPSEC_CRYPTO_ALG_NONE && - sa->integ_alg == IPSEC_INTEG_ALG_NONE) + if ((sa->crypto_alg == IPSEC_CRYPTO_ALG_NONE && + sa->integ_alg == IPSEC_INTEG_ALG_NONE) && + !(itp->itp_flags & IPSEC_PROTECT_ITF)) next = (is_ip4 ? im->esp4_no_crypto_tun_node_index : im->esp6_no_crypto_tun_node_index); |