From 22e6920de8ec2fded221d35dcbc4c29fc30ca6e5 Mon Sep 17 00:00:00 2001 From: ae Date: Wed, 20 May 2015 11:59:53 +0000 Subject: In the reply to SADB_X_SPDGET message use the same sequence number that was in the request. Some IKE deamons expect it will the same. Linux and NetBSD also follow this behaviour. PR: 137309 MFC after: 2 weeks --- sys/netipsec/key.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'sys/netipsec') diff --git a/sys/netipsec/key.c b/sys/netipsec/key.c index 6eae0f5..f642ff4 100644 --- a/sys/netipsec/key.c +++ b/sys/netipsec/key.c @@ -2199,7 +2199,7 @@ key_spddelete2(struct socket *so, struct mbuf *m, } /* - * SADB_X_GET processing + * SADB_X_SPDGET processing * receive * * from the user(?), @@ -2237,7 +2237,8 @@ key_spdget(struct socket *so, struct mbuf *m, const struct sadb_msghdr *mhp) return key_senderror(so, m, ENOENT); } - n = key_setdumpsp(sp, SADB_X_SPDGET, 0, mhp->msg->sadb_msg_pid); + n = key_setdumpsp(sp, SADB_X_SPDGET, mhp->msg->sadb_msg_seq, + mhp->msg->sadb_msg_pid); KEY_FREESP(&sp); if (n != NULL) { m_freem(m); -- cgit v1.1