From 24f486cb563399babf553eb0a09082572ab4a303 Mon Sep 17 00:00:00 2001 From: Dave Barach Date: Wed, 25 Sep 2019 11:27:46 -0400 Subject: misc: add vnet classify filter set support Type: feature Signed-off-by: Dave Barach Change-Id: I79b216d2499df143f53977e5b70382f6f887e0bc (cherry picked from commit f5667c3055dbd6755277f085c6778c2b1104aa6e) --- docs/gettingstarted/developers/vnet.md | 27 ++++++++++++++++++++------- 1 file changed, 20 insertions(+), 7 deletions(-) (limited to 'docs') diff --git a/docs/gettingstarted/developers/vnet.md b/docs/gettingstarted/developers/vnet.md index 826af0a90a9..97336a4cdf2 100644 --- a/docs/gettingstarted/developers/vnet.md +++ b/docs/gettingstarted/developers/vnet.md @@ -497,6 +497,11 @@ These commands have the following optional parameters: on a per-paket basis. Must be >32 and less than 9000. Default value: 512. +- filter - Use the pcap rx / tx / drop trace filter, which must + be configured. Use classify filter pcap... to configure the + filter. The filter will only be executed if the per-interface or + any-interface tests fail. + - intfc _interface_ | _any_ - Used to specify a given interface, or use 'any' to run packet capture on all interfaces. 'any' is the default if not provided. Settings from a previous @@ -521,9 +526,10 @@ These commands have the following optional parameters: ## packet trace capture filtering -The "classify filter" debug CLI command constructs an arbitrary set of - packet classifier tables for use with "pcap rx | tx trace," and - (eventually) with the vpp packet tracer +The "classify filter pcap | " debug CLI command +constructs an arbitrary set of packet classifier tables for use with +"pcap rx | tx | drop trace," and with the vpp packet tracer on a +per-interrface basis. Packets which match a rule in the classifier table chain will be traced. The tables are automatically ordered so that matches in the @@ -540,17 +546,24 @@ and match values. If a classifier table with a suitable mask already exists, the CLI command adds a match rule to the existing table. If not, the CLI command add a new table and the indicated mask rule -### Configure a simple classify filter +### Configure a simple pcap classify filter ``` - classify filter mask l3 ip4 src match l3 ip4 src 192.168.1.11" + classify filter pcap mask l3 ip4 src match l3 ip4 src 192.168.1.11" pcap rx trace on max 100 filter ``` -### Configure another fairly simple filter +### Configure a simple interface packet-tracer filter + +``` + classify filter GigabitEthernet3/0/0 mask l3 ip4 src match l3 ip4 src 192.168.1.11" + [device-driver debug CLI TBD] +``` + +### Configure another fairly simple pcap classify filter ``` - classify filter mask l3 ip4 src dst match l3 ip4 src 192.168.1.10 dst 192.168.2.10 + classify filter pcap mask l3 ip4 src dst match l3 ip4 src 192.168.1.10 dst 192.168.2.10 pcap tx trace on max 100 filter ``` -- cgit 1.2.3-korg