On Wed, 29 May 2013 13:52:55 +0300
Mike Rapoport [off-list ref] wrote:

On Wed, May 29, 2013 at 1:13 PM, Cong Wang [off-list ref] wrote:

quoted

On Wed, 29 May 2013 at 10:00 GMT, Mike Rapoport [off-list ref] wrote:

quoted

Signed-off-by: Mike Rapoport <redacted>
---
 ip/iplink_vxlan.c | 125 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 125 insertions(+)

diff --git a/ip/iplink_vxlan.c b/ip/iplink_vxlan.c
index 1025326..be6c0ac 100644
--- a/ip/iplink_vxlan.c
+++ b/ip/iplink_vxlan.c

@@ -28,11 +28,87 @@ static void explain(void)
      fprintf(stderr, "                 [ port MIN MAX ] [ [no]learning ]\n");
      fprintf(stderr, "                 [ [no]proxy ] [ [no]rsc ]\n");
      fprintf(stderr, "                 [ [no]l2miss ] [ [no]l3miss ]\n");
+     fprintf(stderr, "                 [ dstadd DST ]\n");
+     fprintf(stderr, "                 [ dstdel ADDR ]\n");

Excuse me, but this looks like a design failure as you manipulate
remotes with `ip link` while creating vxlan devices, shouldn't this be
in a standard alone tool if we can't reuse any existing tool? Or am I
missing anything?

Frankly, I had a long hesitation about the userspace implementation.
From one side it seems very logical to use ip/iplink_vxlan for vxlan
device manipulations. Moreover, since the remotes are used pretty much
the same way as the group address, adding the remotes management to
ip/iplink_vxlan makes a lot of sense. Besides, creation of stand alone
tool for remote list manipulation in vxlan seemed to me little bit far
fetched.

On the other hand, I quite agree with you that
ip link add vxlan0 ... dstadd 192.168.1.1
or
ip link set vxlan0 ... dstdel 192.168.1.1
looks weird at least.

Don't like add/delete semantics here either.
Maybe replace or modify, or has this grown enough that having its own
command line tool "vxlan ..." makes sense?