Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Atzm Watanabe <atzm@stratosphere.co.jp>
Cc: <netdev@vger.kernel.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2 v2] vxlan: Allow setting destination to unicast address.
Date: Thu, 11 Apr 2013 18:48:20 +0100	[thread overview]
Message-ID: <1365702500.7355.0.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <87li8pmkvh.wl%atzm@stratosphere.co.jp>

On Thu, 2013-04-11 at 19:17 +0900, Atzm Watanabe wrote:
> This patch allows setting VXLAN destination to unicast address.
> It allows that VXLAN can be used as peer-to-peer tunnel without
> multicast.
> 
> v2: use a new argument "remote" instead of "group" based by
>     Stephen Hemminger's comments.
> 
> Signed-off-by: Atzm Watanabe <atzm@stratosphere.co.jp>
[...]
> --- a/ip/iplink_vxlan.c
> +++ b/ip/iplink_vxlan.c
> @@ -23,7 +23,8 @@
>  
>  static void explain(void)
>  {
> -	fprintf(stderr, "Usage: ... vxlan id VNI [ group ADDR ] [ local ADDR ]\n");
> +	fprintf(stderr, "Usage: ... vxlan id VNI [ group ADDR ] [ remote ADDR ]\n");
[...]

Shouldn't that be "[ group|remote ADDR ]", to show that you can specify
one or the other?

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  parent reply	other threads:[~2013-04-11 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 10:17 [PATCH iproute2 v2] vxlan: Allow setting destination to unicast address Atzm Watanabe
2013-04-11 15:24 ` Stephen Hemminger
2013-04-11 17:30   ` David Miller
2013-04-12  5:31     ` Atzm Watanabe
2013-04-11 17:48 ` Ben Hutchings [this message]
2013-04-12  5:31   ` Atzm Watanabe

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=1365702500.7355.0.camel@bwh-desktop.uk.solarflarecom.com \
    --to=bhutchings@solarflare.com \
    --cc=atzm@stratosphere.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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