From: "Liu, Yong" <yong.liu@intel.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests mac_filter: use scapy to send packets
Date: Fri, 2 Dec 2016 05:44:37 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E6033561C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAP4Qi3_oQ7dmhgARVuvPvJvk42CgdOSB33+f7zGJORg4nDnMGA@mail.gmail.com>
Jianbo, could you explain your usage model? We are now running DTS on tester machine.
> -----Original Message-----
> From: Jianbo Liu [mailto:jianbo.liu@linaro.org]
> Sent: Friday, December 02, 2016 11:45 AM
> To: Liu, Yong
> Cc: dts@dpdk.org
> Subject: Re: [dts] [PATCH] tests mac_filter: use scapy to send packets
>
> Hi Marvin,
>
> On 2 December 2016 at 11:27, Liu, Yong <yong.liu@intel.com> wrote:
> > Hi Jianbo,
> > Packet module is one abstract layer based on scapy. We abstracted this
> layer for monitoring scapy process and integrating sniff/configuration
> function.
> > It should work the same as scapy command. I'm interesting in why your
> intended to use scapy replace of Packet module.
> >
> I assume dts can be run on a different machine from tester. Am I right?
> But I got the following error, as the module sends packets through its
> local port, not the tester's port, but they are different if dts is
> not run on tester machine.
Yes, that's our original plan. But based on time efficiency and real usage model, we assume
Tester and DTS will use same machine.
next prev parent reply other threads:[~2016-12-02 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 2:45 Jianbo Liu
2016-12-02 3:27 ` Liu, Yong
2016-12-02 3:45 ` Jianbo Liu
2016-12-02 5:44 ` Liu, Yong [this message]
2016-12-02 6:06 ` Jianbo Liu
2016-12-02 6:13 ` Liu, Yong
2016-12-02 6:32 ` Jianbo 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=86228AFD5BCD8E4EBFD2B90117B5E81E6033561C@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=jianbo.liu@linaro.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).