From: Sabrina Dubroca <sd@queasysnail.net>
To: netdev@vger.kernel.org
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: [PATCH ipsec-next v4 0/2] xfrm: add IPv6 encapsulation support for ESP over UDP and TCP
Date: Mon, 27 Apr 2020 17:59:33 +0200 [thread overview]
Message-ID: <cover.1588002010.git.sd@queasysnail.net> (raw)
This series adds IPv6 encapsulation of ESP over both UDP and TCP. In
both cases, the code is very similar to the existing IPv4
encapsulation implementation. The core espintcp code is almost
entirely version-independent.
v2: rebase on top of ipsec-next/master
v3: really rebase this time
v4: fix build warning when !_HAVE_ARCH_IPV6_CSUM
Sabrina Dubroca (2):
xfrm: add support for UDPv6 encapsulation of ESP
xfrm: add IPv6 support for espintcp
include/net/ipv6_stubs.h | 5 +
include/net/xfrm.h | 5 +
net/ipv4/Kconfig | 1 +
net/ipv4/udp.c | 10 +-
net/ipv6/Kconfig | 12 ++
net/ipv6/af_inet6.c | 5 +
net/ipv6/ah6.c | 1 +
net/ipv6/esp6.c | 414 +++++++++++++++++++++++++++++++++++---
net/ipv6/esp6_offload.c | 7 +-
net/ipv6/ip6_vti.c | 18 +-
net/ipv6/ipcomp6.c | 1 +
net/ipv6/xfrm6_input.c | 106 +++++++++-
net/ipv6/xfrm6_protocol.c | 48 +++++
net/xfrm/Kconfig | 3 +
net/xfrm/Makefile | 2 +-
net/xfrm/espintcp.c | 56 +++++-
net/xfrm/xfrm_interface.c | 3 +
17 files changed, 647 insertions(+), 50 deletions(-)
--
2.26.2
next reply other threads:[~2020-04-27 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:59 Sabrina Dubroca [this message]
2020-04-27 15:59 ` [PATCH ipsec-next v4 1/2] xfrm: add support for UDPv6 encapsulation of ESP Sabrina Dubroca
2020-04-27 15:59 ` [PATCH ipsec-next v4 2/2] xfrm: add IPv6 support for espintcp Sabrina Dubroca
2020-04-29 7:52 ` [PATCH ipsec-next v4 0/2] xfrm: add IPv6 encapsulation support for ESP over UDP and TCP Steffen Klassert
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=cover.1588002010.git.sd@queasysnail.net \
--to=sd@queasysnail.net \
--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 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).