test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yufen Mo <yufengx.mo@intel.com>
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 1/2] framewok: fixed packet module defect
Date: Thu, 18 Aug 2016 14:33:22 +0800	[thread overview]
Message-ID: <1471502003-25292-2-git-send-email-yufengx.mo@intel.com> (raw)
In-Reply-To: <1471502003-25292-1-git-send-email-yufengx.mo@intel.com>

From: yufengmx <yufengx.mo@intel.com>


add condition for packet address change when src mac is zero,
this process cause that written pcap is not the same as received pcap

Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
 framework/packet.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/framework/packet.py b/framework/packet.py
index 6c892e5..465350f 100755
--- a/framework/packet.py
+++ b/framework/packet.py
@@ -318,7 +318,8 @@ class scapy(object):
         self.print_summary()
         if intf != '':
             # fix fortville can't receive packets with 00:00:00:00:00:00
-            self.pkt.getlayer(0).src = get_if_hwaddr(intf)
+            if self.pkt.getlayer(0).src == "00:00:00:00:00:00":
+                self.pkt.getlayer(0).src = get_if_hwaddr(intf)
             sendp(self.pkt, iface=intf)
 
 
-- 
1.9.3

  reply	other threads:[~2016-08-18  6:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  6:33 [dts] [PATCH V1 0/2] packet capture: update automation testing script/test plan Yufen Mo
2016-08-18  6:33 ` Yufen Mo [this message]
2016-08-18  6:33 ` [dts] [PATCH V1 2/2] Packet capture: upload " Yufen Mo
2016-08-18  9:10   ` Liu, Yong
2016-08-19  1:05     ` Mo, YufengX
2016-08-19  1:17       ` Liu, Yong
  -- strict thread matches above, loose matches on Subject: below --
2016-08-15  3:30 [dts] [PATCH V1 0/2] packet capture: update " Yufen Mo
2016-08-15  3:30 ` [dts] [PATCH V1 1/2] framewok: fixed packet module defect Yufen Mo

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=1471502003-25292-2-git-send-email-yufengx.mo@intel.com \
    --to=yufengx.mo@intel.com \
    --cc=dts@dpdk.org \
    /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).