From: Marvin Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH 0/3] enable random packet check function
Date: Wed, 26 Oct 2016 15:00:38 +0800 [thread overview]
Message-ID: <1477465241-17826-1-git-send-email-yong.liu@intel.com> (raw)
Random packet check function will check packet content in UDP/TCP/IPv6 packets.
Both content and packets sequence will be checked. In first implementation,
packet index saved in L4 source port. But scapy can't correct handle the
packet with some kinds of protocals. So workaround this issue by saveing index
in source ip address.
Marvin Liu (3):
framework utils: add function to convert ipaddress
framework packet: support ip layer elements strip
framework tester: workaround random packet check issue
framework/packet.py | 18 ++++++++++++++++++
framework/tester.py | 31 +++++++++++++++++++++++++------
framework/utils.py | 22 ++++++++++++++++++++++
3 files changed, 65 insertions(+), 6 deletions(-)
--
1.9.3
next reply other threads:[~2016-10-26 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 7:00 Marvin Liu [this message]
2016-10-26 7:00 ` [dts] [PATCH 1/3] framework utils: add function to convert ipaddress Marvin Liu
2016-10-26 7:00 ` [dts] [PATCH 2/3] framework packet: support ip layer elements strip Marvin Liu
2016-10-26 7:00 ` [dts] [PATCH 3/3] framework tester: workaround random packet check issue Marvin Liu
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=1477465241-17826-1-git-send-email-yong.liu@intel.com \
--to=yong.liu@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).