Fri, Nov 16, 2018 at 01:55:13AM CET, amritha.namb...@intel.com wrote: >Added support for filtering based on port ranges. >UAPI changes have been accepted into net-next. > >Example: >1. Match on a port range: >------------------------- >$ tc filter add dev enp4s0 protocol ip parent ffff:\ > prio 1 flower ip_proto tcp dst_port range 20-30 skip_hw\ > action drop > >$ tc -s filter show dev enp4s0 parent ffff: >filter protocol ip pref 1 flower chain 0 >filter protocol ip pref 1 flower chain 0 handle 0x1 > eth_type ipv4 > ip_proto tcp > dst_port range 20-30 > skip_hw > not_in_hw > action order 1: gact action drop > random type none pass val 0 > index 1 ref 1 bind 1 installed 85 sec used 3 sec > Action statistics: > Sent 460 bytes 10 pkt (dropped 10, overlimits 0 requeues 0) > backlog 0b 0p requeues 0 > >2. Match on IP address and port range: >-------------------------------------- >$ tc filter add dev enp4s0 protocol ip parent ffff:\ > prio 1 flower dst_ip 192.168.1.1 ip_proto tcp dst_port range 100-200\ > skip_hw action drop > >$ tc -s filter show dev enp4s0 parent ffff: >filter protocol ip pref 1 flower chain 0 handle 0x2 > eth_type ipv4 > ip_proto tcp > dst_ip 192.168.1.1 > dst_port range 100-200 > skip_hw > not_in_hw > action order 1: gact action drop > random type none pass val 0 > index 2 ref 1 bind 1 installed 58 sec used 2 sec > Action statistics: > Sent 920 bytes 20 pkt (dropped 20, overlimits 0 requeues 0) > backlog 0b 0p requeues 0 > >v3: >Modified flower_port_range_attr_type calls. > >v2: >Addressed Jiri's comment to sync output format with input > >Signed-off-by: Amritha Nambiar <amritha.namb...@intel.com>
Looks ok. But why do you have man changes in a separate patch ? I think it should be in this one. Anyway Acked-by: Jiri Pirko <j...@mellanox.com>
