Skip to content

Commit

Permalink
doc: fix tap guide
Browse files Browse the repository at this point in the history
[ upstream commit 781088d ]

Corrected one typo and IP address according RFC5735.

Fixes: de96fe6 ("net/tap: add basic flow API patterns and actions")

Signed-off-by: Andrzej Ostruszka <aostruszka@marvell.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
  • Loading branch information
Andrzej Ostruszka authored and kevintraynor committed Dec 11, 2019
1 parent c269e97 commit abb5b30
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/guides/nics/tap.rst
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ Please change the IP addresses as you see fit.

If routing is enabled on the host you can also communicate with the DPDK App
over the internet via a standard socket layer application as long as you
account for the protocol handing in the application.
account for the protocol handling in the application.

If you have a Network Stack in your DPDK application or something like it you
can utilize that stack to handle the network protocols. Plus you would be able
Expand Down Expand Up @@ -132,9 +132,9 @@ As rules are translated to TC, it is possible to show them with something like::
Examples of testpmd flow rules
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Drop packets for destination IP 192.168.0.1::
Drop packets for destination IP 192.0.2.1::

testpmd> flow create 0 priority 1 ingress pattern eth / ipv4 dst is 1.1.1.1 \
testpmd> flow create 0 priority 1 ingress pattern eth / ipv4 dst is 192.0.2.1 \
/ end actions drop / end

Ensure packets from a given MAC address are received on a queue 2::
Expand Down

0 comments on commit abb5b30

Please sign in to comment.