From: Martin Varghese <martinvarghesenokia@gmail.com>
To: netdev@vger.kernel.org, davem@davemloft.net, corbet@lwn.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
scott.drennan@nokia.com, jbenc@redhat.com,
martin.varghese@nokia.com
Subject: [PATCH v3 net-next 0/2] Bare UDP L3 Encapsulation Module
Date: Sat, 16 Nov 2019 11:13:32 +0530 [thread overview]
Message-ID: <cover.1573872263.git.martin.varghese@nokia.com> (raw)
From: Martin Varghese <martin.varghese@nokia.com>
There are various L3 encapsulation standards using UDP being discussed to
leverage the UDP based load balancing capability of different networks.
MPLSoUDP (https://tools.ietf.org/html/rfc7510) is one among them.
The Bareudp tunnel module provides a generic L3 encapsulation tunnelling
support for tunnelling different L3 protocols like MPLS, IP, NSH etc. inside
a UDP tunnel.
Special Handling
----------------
The bareudp device supports special handling for MPLS & IP as they can have
multiple ethertypes.
MPLS procotcol can have ethertypes 0x8847 (unicast) & 0x8848 (multicast).
IP proctocol can have ethertypes 0x0800 (v4) & 0x86dd (v6).
This special handling can be enabled only for ethertype 0x0800 & 0x8847 with a
flag called extended mode.
Usage
------
1. Device creation & deletion
a. ip link add dev bareudp0 type bareudp dstport 6635 ethertype 0x8847
This creates a bareudp tunnel device which tunnels L3 traffic with ethertype
0x8847 (MPLS traffic). The destination port of the UDP header will be set to 6635
The device will listen on UDP port 6635 to receive traffic.
b. ip link delete bareudp0
2. Device creation with extended mode enabled
There are two ways to create a bareudp device for MPLS & IP with extended mode
enabled.
a. ip link add dev bareudp0 type bareudp dstport 6635 ethertype 0x8847 extmode 1
b. ip link add dev bareudp0 type bareudp dstport 6635 ethertype mpls
Why not FOU ?
------------
FOU by design does l4 encapsulation.It maps udp port to ipproto (IP protocol number
for l4 protocol).
Bareudp acheives a generic l3 encapsulation.It maps udp port to l3 ethertype
For example in the case of MPLS -
In the egress direction an MPLS packet "eth header | mpls header | payload" is
encapsulated to "eth header | ip header | udp header | mpls header | payload"
In the Ingress direction the udp tunnel packet
"eth header | ip header | udp header | mpls header | payload" is decapsulated to
"eth header | mpls header | payload"
Martin Varghese (2):
UDP tunnel encapsulation module for tunnelling different protocols
like MPLS,IP,NSH etc.
Special handling for IP & MPLS.
Documentation/networking/bareudp.rst | 44 ++
Documentation/networking/index.rst | 1 +
drivers/net/Kconfig | 13 +
drivers/net/Makefile | 1 +
drivers/net/bareudp.c | 876 +++++++++++++++++++++++++++++++++++
include/net/bareudp.h | 20 +
include/net/ip6_tunnel.h | 45 ++
include/net/ip_tunnels.h | 42 ++
include/uapi/linux/if_link.h | 13 +
9 files changed, 1055 insertions(+)
create mode 100644 Documentation/networking/bareudp.rst
create mode 100644 drivers/net/bareudp.c
create mode 100644 include/net/bareudp.h
--
1.8.3.1
next reply other threads:[~2019-11-16 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 5:43 Martin Varghese [this message]
2019-11-16 5:44 ` [PATCH v3 net-next 1/2] UDP tunnel encapsulation module for tunnelling different protocols like MPLS,IP,NSH etc Martin Varghese
2019-11-18 17:23 ` Willem de Bruijn
2019-11-28 16:24 ` Martin Varghese
2019-11-29 18:18 ` Willem de Bruijn
2019-12-31 15:32 ` Martin Varghese
2020-01-02 19:55 ` Willem de Bruijn
2019-11-20 11:10 ` kbuild test robot
2019-11-16 5:45 ` [PATCH v3 net-next 2/2] Special handling for IP & MPLS Martin Varghese
2019-11-18 17:30 ` Willem de Bruijn
2019-11-28 16:12 ` Martin Varghese
2019-11-29 18:20 ` Willem de Bruijn
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.1573872263.git.martin.varghese@nokia.com \
--to=martinvarghesenokia@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=scott.drennan@nokia.com \
--cc=yoshfuji@linux-ipv6.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).