On Mon, 6 Feb 2017 09:44:00 +0100
Simon Horman wrote:
> On Thu, Feb 02, 2017 at 06:27:48PM +0100, Jiri Pirko wrote:
> > Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.com wrote:
> > >Allow matching on Neighbour Discovery target IP, and source and
> > >destination link-layer address
On Mon, Feb 06, 2017 at 10:44:59AM +0100, Jiri Pirko wrote:
> Mon, Feb 06, 2017 at 09:44:00AM CET, simon.hor...@netronome.com wrote:
> >On Thu, Feb 02, 2017 at 06:27:48PM +0100, Jiri Pirko wrote:
> >> Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.com wrote:
> >> >Allow matching on Nei
Mon, Feb 06, 2017 at 09:44:00AM CET, simon.hor...@netronome.com wrote:
>On Thu, Feb 02, 2017 at 06:27:48PM +0100, Jiri Pirko wrote:
>> Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.com wrote:
>> >Allow matching on Neighbour Discovery target IP, and source and
>> >destination link-laye
On Thu, Feb 02, 2017 at 06:27:48PM +0100, Jiri Pirko wrote:
> Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.com wrote:
> >Allow matching on Neighbour Discovery target IP, and source and
> >destination link-layer addresses for neighbour solicitation and
> >advertisement messages.
> >
>
Thu, Feb 02, 2017 at 11:38:40AM CET, simon.hor...@netronome.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 et
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 : flower \
indev eth0 ip_proto icmpv6 type 1
