From 781088dad55b840e04e699071d443f9ecfc208b3 Mon Sep 17 00:00:00 2001 From: Andrzej Ostruszka Date: Thu, 21 Nov 2019 14:27:01 +0100 Subject: [PATCH] doc: fix tap guide Corrected one typo and IP address according RFC5735. Fixes: de96fe68ae95 ("net/tap: add basic flow API patterns and actions") Cc: stable@dpdk.org Signed-off-by: Andrzej Ostruszka Reviewed-by: Ferruh Yigit --- doc/guides/nics/tap.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst index 85c7b895ae..7e44f84620 100644 --- a/doc/guides/nics/tap.rst +++ b/doc/guides/nics/tap.rst @@ -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 @@ -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:: -- 2.20.1