lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 2 Dec 2013 23:51:01 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Hangbin Liu <liuhangbin@...il.com>
Cc:	network dev <netdev@...r.kernel.org>
Subject: Re: [patch iproute2] ipneigh: update ip neigh usage

On Fri, 29 Nov 2013 22:37:40 +0800
Hangbin Liu <liuhangbin@...il.com> wrote:

> From function nud_state_a2n we can see there are more states could be used. So
> update the ip neigh usage.
> 
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
> ---
>  ip/ipneigh.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/ip/ipneigh.c b/ip/ipneigh.c
> index d76e035..c203775 100644
> --- a/ip/ipneigh.c
> +++ b/ip/ipneigh.c
> @@ -46,9 +46,12 @@ static void usage(void) __attribute__((noreturn));
>  static void usage(void)
>  {
>  	fprintf(stderr, "Usage: ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ]\n"
> -		        "          [ nud { permanent | noarp | stale | reachable } ]\n"
> -		        "          | proxy ADDR } [ dev DEV ]\n");
> +		        "                    [ nud STATE ] | proxy ADDR } [ dev DEV ]\n");
> +	fprintf(stderr, "\n");
>  	fprintf(stderr, "       ip neigh {show|flush} [ to PREFIX ] [ dev DEV ] [ nud STATE ]\n");
> +	fprintf(stderr, "\n");
> +	fprintf(stderr, "STATE := { permanent | reachable | noarp | none | stale |\n");
> +	fprintf(stderr, "           incomplete | delay | probe | failed }\n");
>  	exit(-1);
>  }
>  

Accepted.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ