From: Simon Horman <simon.horman@netronome.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH/RFC net-next 0/4] net: support MPLS in IPv4 and UDP
Date: Thu, 7 Jul 2016 07:38:16 +0200 [thread overview]
Message-ID: <20160707053814.GB10002@penelope.isobedori.kobe.vergenet.net> (raw)
In-Reply-To: <CALx6S36-zs0SEYgKz4koRhsAaadPaWh_w4SYczp_MwxALKqO5w@mail.gmail.com>
On Wed, Jul 06, 2016 at 09:44:13PM -0700, Tom Herbert wrote:
> On Wed, Jul 6, 2016 at 11:22 AM, Simon Horman
> <simon.horman@netronome.com> wrote:
> > 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.
> >
>
> HI Siomon,
>
> Thanks for these patches! Can provide the commands for testing this?
Sure, will do.
next prev parent reply other threads:[~2016-07-07 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 18:22 [PATCH/RFC net-next 0/4] net: support MPLS in IPv4 and UDP Simon Horman
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 [this message]
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=20160707053814.GB10002@penelope.isobedori.kobe.vergenet.net \
--to=simon.horman@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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.