From: Rami Rosen <rami.rosen@intel.com>
To: yong.liu@intel.com
Cc: dts@dpdk.org, Rami Rosen <rami.rosen@intel.com>
Subject: [dts] [PATCH] test_plans kni: use correct interface in routing tests.
Date: Fri, 25 Aug 2017 00:38:15 +0300 [thread overview]
Message-ID: <20170824213815.21610-1-rami.rosen@intel.com> (raw)
This patch fixes the two routing modes tests in kni test plan
to use the correct interfaces; the second interface should be
in both cases vEth3_0 and not vEth2_0.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
test_plans/kni_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test_plans/kni_test_plan.rst b/test_plans/kni_test_plan.rst
index 2f1b65b60e9d..fc10f5eab5ab 100644
--- a/test_plans/kni_test_plan.rst
+++ b/test_plans/kni_test_plan.rst
@@ -560,7 +560,7 @@ The application is launched and the bridge is setup using the commands below::
./build/app/kni -c <Core mask> -n 4 -- -P -p <Port mask> --config="<Ports/Cores configuration>" &
ifconfig vEth2_0 192.170.2.1
- ifconfig vEth2_0 192.170.3.1
+ ifconfig vEth3_0 192.170.3.1
route add -net 192.170.2.0 netmask 255.255.255.0 gw 192.170.2.1
route add -net 192.170.3.0 netmask 255.255.255.0 gw 192.170.3.1
arp -s 192.170.2.2 vEth2_0
@@ -593,7 +593,7 @@ Set up the interfaces and the bridge::
echo 1 > /proc/sys/net/ipv4/ip_forward
rmmod rte_kni
ifconfig vEth2_0 192.170.2.1
- ifconfig vEth2_0 192.170.3.1
+ ifconfig vEth3_0 192.170.3.1
route add -net 192.170.2.0 netmask 255.255.255.0 gw 192.170.2.1
route add -net 192.170.3.0 netmask 255.255.255.0 gw 192.170.3.1
arp -s 192.170.2.2 vEth2_0
--
2.11.0
next reply other threads:[~2017-08-24 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 21:38 Rami Rosen [this message]
2017-08-25 11:28 ` Liu, Yong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170824213815.21610-1-rami.rosen@intel.com \
--to=rami.rosen@intel.com \
--cc=dts@dpdk.org \
--cc=yong.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).