From: Martin Varghese <martinvarghesenokia@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
corbet@lwn.net, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
scott.drennan@nokia.com, Jiri Benc <jbenc@redhat.com>,
martin.varghese@nokia.com
Subject: Re: [PATCH net-next v4 2/2] net: Special handling for IP & MPLS.
Date: Thu, 23 Jan 2020 15:30:11 +0530 [thread overview]
Message-ID: <20200123100011.GB6331@martin-VirtualBox> (raw)
In-Reply-To: <CA+FuTSdvC+7MuEPnB2kUxx+L5170SxEP1Gn6AfN5v6e5_RqcvQ@mail.gmail.com>
On Wed, Jan 22, 2020 at 01:30:53PM -0500, Willem de Bruijn wrote:
> On Tue, Jan 21, 2020 at 12:51 PM Martin Varghese
> <martinvarghesenokia@gmail.com> wrote:
> >
> > From: Martin Varghese <martin.varghese@nokia.com>
> >
> > Special handling is needed in bareudp module for IP & MPLS as they
> > support more than one ethertypes.
> >
> > MPLS has 2 ethertypes. 0x8847 for MPLS unicast and 0x8848 for MPLS multicast.
> > While decapsulating MPLS packet from UDP packet the tunnel destination IP
> > address is checked to determine the ethertype. The ethertype of the packet
> > will be set to 0x8848 if the tunnel destination IP address is a multicast
> > IP address. The ethertype of the packet will be set to 0x8847 if the
> > tunnel destination IP address is a unicast IP address.
> >
> > IP has 2 ethertypes.0x0800 for IPV4 and 0x86dd for IPv6. The version
> > field of the IP header tunnelled will be checked to determine the ethertype.
> >
> > This special handling to tunnel additional ethertypes will be disabled
> > by default and can be enabled using a flag called ext mode. This flag can
> > be used only with ethertypes 0x8847 and 0x0800.
> >
> > Signed-off-by: Martin Varghese <martin.varghese@nokia.com>
>
> Acked-by: Willem de Bruijn <willemb@google.com>
Thanks for your time.
prev parent reply other threads:[~2020-01-23 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:48 [PATCH net-next v4 0/2] Bare UDP L3 Encapsulation Module Martin Varghese
2020-01-21 17:50 ` [PATCH net-next v4 1/2] net: UDP tunnel encapsulation module for Martin Varghese
2020-01-22 18:29 ` Willem de Bruijn
2020-01-23 9:59 ` Martin Varghese
2020-01-23 14:50 ` Martin Varghese
2020-01-24 9:41 ` kbuild test robot
2020-01-24 13:30 ` kbuild test robot
2020-01-21 17:51 ` [PATCH net-next v4 2/2] net: Special handling for IP & MPLS Martin Varghese
2020-01-22 18:30 ` Willem de Bruijn
2020-01-23 10:00 ` Martin Varghese [this message]
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=20200123100011.GB6331@martin-VirtualBox \
--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=willemdebruijn.kernel@gmail.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).