From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dan Williams <dcbw@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] ipv6: Add support for IPsec virtual tunnel interfaces
Date: Tue, 27 Aug 2013 13:08:36 +0200 [thread overview]
Message-ID: <20130827110836.GE7660@secunet.com> (raw)
In-Reply-To: <1377535058.11709.21.camel@dcbw.foobar.com>
On Mon, Aug 26, 2013 at 11:37:38AM -0500, Dan Williams wrote:
> On Mon, 2013-08-19 at 08:27 +0200, Steffen Klassert wrote:
> > This patch adds IPv6 support for IPsec virtual tunnel interfaces
> > (vti). IPsec virtual tunnel interfaces provide a routable interface
> > for IPsec tunnel endpoints.
>
> Are new ioctls for this kind of thing kosher? Or should it be using
> netlink instead?
>
Well, I used the existing interface that all tunnels use. In particular
the vti tunnel for ipv4 uses it and the ipv6 side should be similar.
We could extend the netlink interface for tunnels of course, but that's
another issue.
next prev parent reply other threads:[~2013-08-27 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 6:26 [PATCH RFC 0/2] Add IPsec virtual tunnel interfaces to IPv6 Steffen Klassert
2013-08-19 6:26 ` [PATCH RFC 1/2] ipv6: Add a receive path hook for vti6 in xfrm6_mode_tunnel Steffen Klassert
2013-08-19 6:27 ` [PATCH RFC 2/2] ipv6: Add support for IPsec virtual tunnel interfaces Steffen Klassert
2013-08-22 7:47 ` Fan Du
2013-08-23 6:12 ` Steffen Klassert
2013-08-23 6:17 ` Fan Du
2013-08-26 16:37 ` Dan Williams
2013-08-26 16:51 ` Eric Dumazet
2013-08-27 11:08 ` Steffen Klassert [this message]
2013-08-21 0:28 ` [PATCH RFC 0/2] Add IPsec virtual tunnel interfaces to IPv6 David Miller
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=20130827110836.GE7660@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dcbw@redhat.com \
--cc=netdev@vger.kernel.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 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.