netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: "Liu, Mengke" <mengke.liu@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Question]: iproute2 extension for supporting lightweight tunnel
Date: Thu, 15 Oct 2015 11:23:49 +0200	[thread overview]
Message-ID: <20151015112349.44623b07@griffin> (raw)
In-Reply-To: <7DDE0CBD3BECA4418AF34146552BC32B08C3E1B9@SHSMSX104.ccr.corp.intel.com>

On Thu, 15 Oct 2015 06:26:30 +0000, Liu, Mengke wrote:
> I am trying to use the "lightweight tunnels" after building the Linux
> kernel from source with "Lightweight & flow based encapsulation"
> support. Can you tell me how to get iproute2 extension for supporting
> the following  command in commit log(commit ID
> e69724f32e62502a6e686eae36b7aadfeea60dca)
>        "ip route add 40.1.1.1/32 encap vxlan id 10 dst 50.1.1.2 dev
> vxlan0" 

This is not yet merged. AFAIK Thomas is going to post a patchset to add
this to iproute in a few days.

 Jiri

-- 
Jiri Benc

      reply	other threads:[~2015-10-15  9:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  6:26 [Question]: iproute2 extension for supporting lightweight tunnel Liu, Mengke
2015-10-15  9:23 ` Jiri Benc [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=20151015112349.44623b07@griffin \
    --to=jbenc@redhat.com \
    --cc=mengke.liu@intel.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).