[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01b41b92-1cba-a81f-523c-99c00750538a@gmail.com>
Date: Wed, 7 Nov 2018 13:03:34 -0700
From: David Ahern <dsahern@...il.com>
To: Stefano Brivio <sbrivio@...hat.com>
Cc: netdev@...r.kernel.org,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: [PATCH iproute2 net-next 1/2] iplink_vxlan: Add DF configuration
On 11/6/18 2:39 PM, Stefano Brivio wrote:
> diff --git a/ip/iplink_vxlan.c b/ip/iplink_vxlan.c
> index 7fc0e2b4eb06..86afbe1334f0 100644
> --- a/ip/iplink_vxlan.c
> +++ b/ip/iplink_vxlan.c
> @@ -31,6 +31,7 @@ static void print_explain(FILE *f)
> " [ local ADDR ]\n"
> " [ ttl TTL ]\n"
> " [ tos TOS ]\n"
> + " [ df DF ]\n"
> " [ flowlabel LABEL ]\n"
> " [ dev PHYS_DEV ]\n"
> " [ dstport PORT ]\n"
Since it is the df bit, that user option seems fine to me. Should be ok
to use that for your probe on iproute2 support.
That said, the man-page update should spell out what df refers to.
Powered by blists - more mailing lists