From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, simon.horman@netronome.com,
Jiri Benc <jbenc@redhat.com>, Thomas Graf <tgraf@suug.ch>,
u9012063@gmail.com
Subject: [PATCH net-next 0/5] lwtunnel: add ip and ip6 options setting and dumping
Date: Wed, 6 Nov 2019 17:01:02 +0800 [thread overview]
Message-ID: <cover.1573030805.git.lucien.xin@gmail.com> (raw)
With this patchset, users can configure options by ip route encap
for geneve, vxlan and ersapn lwtunnel, like:
# ip r a 1.1.1.0/24 encap ip id 1 geneve class 0 type 0 \
data "1212121234567890" dst 10.1.0.2 dev geneve1
# ip r a 1.1.1.0/24 encap ip id 1 vxlan gbp 456 \
dst 10.1.0.2 dev erspan1
# ip r a 1.1.1.0/24 encap ip id 1 erspan ver 1 idx 123 \
dst 10.1.0.2 dev erspan1
iproute side patch is attached on the reply of this mail.
Thank Simon for good advice.
Xin Long (5):
lwtunnel: add options process for arp request
lwtunnel: add options process for cmp_encap
lwtunnel: add options setting and dumping for geneve
lwtunnel: add options setting and dumping for vxlan
lwtunnel: add options setting and dumping for erspan
include/uapi/linux/lwtunnel.h | 41 +++++
net/ipv4/ip_tunnel_core.c | 382 +++++++++++++++++++++++++++++++++++++++---
2 files changed, 402 insertions(+), 21 deletions(-)
--
2.1.0
next reply other threads:[~2019-11-06 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:01 Xin Long [this message]
2019-11-06 9:01 ` [PATCH net-next 1/5] lwtunnel: add options process for arp request Xin Long
2019-11-06 9:01 ` [PATCH net-next 2/5] lwtunnel: add options process for cmp_encap Xin Long
2019-11-06 9:01 ` [PATCH net-next 3/5] lwtunnel: add options setting and dumping for geneve Xin Long
2019-11-06 9:01 ` [PATCH net-next 4/5] lwtunnel: add options setting and dumping for vxlan Xin Long
2019-11-06 9:01 ` [PATCH net-next 5/5] lwtunnel: add options setting and dumping for erspan Xin Long
2019-11-06 9:03 ` [PATCH net-next 0/5] lwtunnel: add ip and ip6 options setting and dumping Xin Long
2019-11-07 5:14 ` David Miller
2019-11-07 10:50 ` Xin Long
2019-11-07 16:18 ` David Ahern
2019-11-08 14:08 ` Xin Long
2019-11-08 15:29 ` David Ahern
2019-11-07 18:34 ` 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=cover.1573030805.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=tgraf@suug.ch \
--cc=u9012063@gmail.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.