[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Feb 2017 18:27:48 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Simon Horman <simon.horman@...ronome.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Dinan Gunawardena <dinan.gunawardena@...ronome.com>,
netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH iproute2/net-next 7/7] tc: flower: Support matching on ND
Thu, Feb 02, 2017 at 11:38:40AM CET, simon.horman@...ronome.com wrote:
>Allow matching on Neighbour Discovery target IP, and source and
>destination link-layer addresses for neighbour solicitation and
>advertisement messages.
>
>Sample usage:
>
>tc qdisc add dev eth0 ingress
>
>tc filter add dev eth0 protocol ipv6 parent ffff: flower \
> indev eth0 ip_proto icmpv6 type 136 code 0 \
> nd_target 2001:470:7eb3:403:201:8eff:fe22:8fea \
> nd_tll 00:01:8e:22:8f:ea action drop
>
>Signed-off-by: Simon Horman <simon.horman@...ronome.com>
Why you are adding this to iproute2? You only poster RFC for kernel.
Please push to kernel first, let it merge, then send iproute2 support.
Powered by blists - more mailing lists