From: Alexander Aring <aring@mojatatu.com>
To: Lucas Bates <lucasb@mojatatu.com>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Marcelo Ricardo Leitner <mleitner@redhat.com>,
Vlad Buslov <vladbu@mellanox.com>,
Davide Caratti <dcaratti@redhat.com>,
kernel@mojatatu.com
Subject: Re: [PATCH v2 net-next 3/3] tc-testing: introduce scapyPlugin for basic traffic
Date: Tue, 9 Jul 2019 11:10:40 -0400 [thread overview]
Message-ID: <20190709151040.unyrfau2ajypqcl4@x220t> (raw)
In-Reply-To: <CAMDBHYKwxnJYMp97vMmhZR5unqT7LyXivhqFm+-Vc59LMqmO4A@mail.gmail.com>
On Mon, Jul 08, 2019 at 09:28:09PM -0400, Lucas Bates wrote:
> Sorry Alex, I completely forgot about this email.
> On Thu, Jul 4, 2019 at 4:29 PM Alexander Aring <aring@mojatatu.com> wrote:
> >
> > Hi,
> >
> > On Wed, Jul 03, 2019 at 08:45:02PM -0400, Lucas Bates wrote:
> > > The scapyPlugin allows for simple traffic generation in tdc to
> > > test various tc features. It was tested with scapy v2.4.2, but
> > > should work with any successive version.
> > Is there a way to introduce thrid party scapy level descriptions which
> > are not upstream yet?
>
> Upstream to scapy? Not yet. This version of the plugin is extremely
> simple, and good for basic traffic. I'll add features to it so we can
> get more creative with the packets that can be sent, though.
>
Can you add this now? I have some tests here for ife and I am on the way
to send it upstream to scapy.
So far this isn't done yet, I like to provide them via a external
directory in the tctesting directory.
Thanks.
- Alex
next prev parent reply other threads:[~2019-07-09 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 0:44 [PATCH v2 net-next 0/3] tc-testing: Add JSON verification and simple traffic generation Lucas Bates
2019-07-04 0:45 ` [PATCH v2 net-next 1/3] tc-testing: Add JSON verification to tdc Lucas Bates
2019-07-04 20:21 ` Alexander Aring
2019-07-08 16:48 ` Lucas Bates
2019-07-08 17:24 ` Alexander Aring
2019-07-09 1:17 ` Lucas Bates
2019-07-04 0:45 ` [PATCH v2 net-next 2/3] tc-testing: Allow tdc plugins to see test case data Lucas Bates
2019-07-04 0:45 ` [PATCH v2 net-next 3/3] tc-testing: introduce scapyPlugin for basic traffic Lucas Bates
2019-07-04 20:29 ` Alexander Aring
2019-07-09 1:28 ` Lucas Bates
2019-07-09 15:10 ` Alexander Aring [this message]
2019-07-08 1:57 ` [PATCH v2 net-next 0/3] tc-testing: Add JSON verification and simple traffic generation David Miller
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=20190709151040.unyrfau2ajypqcl4@x220t \
--to=aring@mojatatu.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=lucasb@mojatatu.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vladbu@mellanox.com \
--cc=xiyou.wangcong@gmail.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