From: Simon Horman <simon.horman@netronome.com>
To: netdev@vger.kernel.org
Subject: [PATCH/RFC net-next 0/4] net: support MPLS in IPv4 and UDP
Date: Wed, 6 Jul 2016 20:22:31 +0200 [thread overview]
Message-ID: <1467829355-4498-1-git-send-email-simon.horman@netronome.com> (raw)
This short series provides support for MPLS in IPv4 (RFC4023), and by
virtue of FOU, MPLS in UDP (RFC7510).
The changes are as follows:
1. Teach tunnel4.c about AF_MPLS, it already understands AF_INET and
AF_INET6
2. Enhance IPIP and SIT to handle MPLS. Both already handle IPv4.
SIT also already handles IPv6.
3. Trivially enhance MPLS to allow routes over SIT and IPIP tunnels.
A corresponding iproute2 patchset will also be posted.
Simon Horman (4):
tunnels: support MPLS over IPv4 tunnels
sit: support MPLS over IPv4
ipip: support MPLS over IPv4
mpls: allow routes on ipip and sit devices
net/ipv4/ipip.c | 137 ++++++++++++++++++++++++++++++++++++++++++++++-------
net/ipv4/tunnel4.c | 77 ++++++++++++++++++++++++++----
net/ipv6/sit.c | 93 +++++++++++++++++++++++++++++-------
net/mpls/af_mpls.c | 6 ++-
4 files changed, 269 insertions(+), 44 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2016-07-06 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 18:22 Simon Horman [this message]
2016-07-06 18:22 ` [PATCH/RFC net-next 1/4] tunnels: support MPLS over IPv4 tunnels Simon Horman
2016-07-06 18:22 ` [PATCH/RFC net-next 2/4] sit: support MPLS over IPv4 Simon Horman
2016-07-07 5:10 ` David Miller
2016-07-07 5:37 ` Simon Horman
2016-07-06 18:22 ` [PATCH/RFC net-next 3/4] ipip: " Simon Horman
2016-07-06 18:22 ` [PATCH/RFC net-next 4/4] mpls: allow routes on ipip and sit devices Simon Horman
2016-07-07 4:44 ` [PATCH/RFC net-next 0/4] net: support MPLS in IPv4 and UDP Tom Herbert
2016-07-07 5:38 ` Simon Horman
2016-07-07 5:12 ` 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=1467829355-4498-1-git-send-email-simon.horman@netronome.com \
--to=simon.horman@netronome.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 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).