diff options
Diffstat (limited to 'docs/gettingstarted/developers/vnet.md')
| -rw-r--r-- | docs/gettingstarted/developers/vnet.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/gettingstarted/developers/vnet.md b/docs/gettingstarted/developers/vnet.md index 89169efb8d4..f9d7bd597fa 100644 --- a/docs/gettingstarted/developers/vnet.md +++ b/docs/gettingstarted/developers/vnet.md @@ -325,7 +325,7 @@ these data to easily filter/track single packets as they traverse the forwarding graph. Multiple records per packet are normal, and to be expected. Packets -will appear multipe times as they traverse the vpp forwarding +will appear multiple times as they traverse the vpp forwarding graph. In this way, vpp graph dispatch traces are significantly different from regular network packet captures from an end-station. This property complicates stateful packet analysis. @@ -494,7 +494,7 @@ These commands have the following optional parameters: capture is off. - <b>max-bytes-per-pkt _nnnn_</b> - maximum number of bytes to trace - on a per-paket basis. Must be >32 and less than 9000. Default value: + on a per-packet basis. Must be >32 and less than 9000. Default value: 512. - <b>filter</b> - Use the pcap rx / tx / drop trace filter, which must @@ -529,7 +529,7 @@ These commands have the following optional parameters: The "classify filter pcap | <interface-name> " 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. +per-interface basis. Packets which match a rule in the classifier table chain will be traced. The tables are automatically ordered so that matches in the @@ -538,7 +538,7 @@ most specific table are tried first. It's reasonably likely that folks will configure a single table with one or two matches. As a result, we configure 8 hash buckets and 128K of match rule space by default. One can override the defaults by -specifiying "buckets <nnn>" and "memory-size <xxx>" as desired. +specifying "buckets <nnn>" and "memory-size <xxx>" as desired. To build up complex filter chains, repeatedly issue the classify filter debug CLI command. Each command must specify the desired mask |