Re: [PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly

2017-01-20 Thread Stephen Hemminger
On Thu, 19 Jan 2017 16:27:53 +0200 Paul Blakey wrote: > Instead of "magic numbers" we can now specify each flag > by name. Prefix of "no" (e.g nofrag) unsets the flag, > otherwise it wil be set. > > Example: > # add a flower filter that will drop fragmented packets >

Re: [PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly

2017-01-19 Thread Or Gerlitz
On 1/19/2017 4:27 PM, Paul Blakey wrote: Hi, added a framework to add new flags more easily, such as the upcoming tcp_flags (see kernel cls_flower), and other ip_flags. FWIW, just wanted to make a note that I have the patches for tcp_flags under the works, so if someone needs them urgently

Re: [PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly

2017-01-19 Thread Jiri Benc
On Thu, 19 Jan 2017 16:27:53 +0200, Paul Blakey wrote: > Instead of "magic numbers" we can now specify each flag > by name. Prefix of "no" (e.g nofrag) unsets the flag, > otherwise it wil be set. > > Example: > # add a flower filter that will drop fragmented packets > tc filter add dev

[PATCH iproute2 net-next V5] tc: flower: Refactor matching flags to be more user friendly

2017-01-19 Thread Paul Blakey
Instead of "magic numbers" we can now specify each flag by name. Prefix of "no" (e.g nofrag) unsets the flag, otherwise it wil be set. Example: # add a flower filter that will drop fragmented packets tc filter add dev ens4f0 protocol ip parent : \ flower \