All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PKTGEN] dumb question: how to start packet TX and set the payload
Date: Thu, 21 Jan 2016 15:09:16 -0500	[thread overview]
Message-ID: <20160121200916.GB11016@mhcomputing.net> (raw)
In-Reply-To: <88FD4A1B-A860-4488-96E0-28D6C544204B@intel.com>

On Thu, Jan 21, 2016 at 07:44:21PM +0000, Wiles, Keith wrote:
> What type of data do you want to add to the packets? Now it builds 
> IPv4/UDP/TCP packets, do you need to replace UDP or TCP or just add more 
> protocol layers?

I perform content inspection of various types:

IPv4 - supported
IPv6 - supported
TCP - supported
UDP - supported
DNS - need custom binary payload
sFlow - need custom binary payload
Netflow - need custom sequence (supported) and custom binary payload
UDP Syslog - need custom ASCII payload (binary would of course work)

TCP Syslog - need custom ASCII payload (probably impossible w/ this tool as a 
three-way handshake is needed for me to begin receiving in the app, which is 
among other things a high performance Syslog digester, but UDP is enough for 
now)

Because it's a security app I have to model things like "99% boring, 1% 
interesting" as packets which raise alerts cost more resources than packets 
which do not.

Matthew.

      reply	other threads:[~2016-01-21 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  6:15 [PKTGEN] dumb question: how to start packet TX and set the payload Matthew Hall
2016-01-21 15:01 ` Wiles, Keith
2016-01-21 19:01   ` Matthew Hall
2016-01-21 15:05 ` Wiles, Keith
2016-01-21 19:00   ` Matthew Hall
2016-01-21 19:44     ` Wiles, Keith
2016-01-21 20:09       ` Matthew Hall [this message]

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=20160121200916.GB11016@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.