DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: harshavardhan Reddy <hvreddy1110@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Intel DPDK support for ntop DPI
Date: Mon, 16 Feb 2015 16:58:05 -0800	[thread overview]
Message-ID: <20150217005805.GA30617@mhcomputing.net> (raw)
In-Reply-To: <CAERxyUXBd8=r9e8-LOkcdG_NgRKK3pbgmi_u4whNQJudA9gXDg@mail.gmail.com>

I did some research on this previously before concluding NDPI wouldn't help me 
much with my own particular application.

Just for running NDPI DPDK is not strictly needed, as NDPI is normally 
read-only so something like PF_RING would work in default ntop / ndpi. If 
you're trying to use NDPI in a read-write application then you'd need to make 
the integration yourself.

However the much harder part than just the integration would be tracking 
flow-starts for TCP and UDP sockets to feed to NDPI. From what I found NDPI by 
itself does not appear to offer connection tracking. It has to be implemented 
separately.

My advice: carefully research how ntop calls ndpi in their code using cscope. 
Because the ndpi documentation about how to use all the functions is kind of 
bad and not so clear. It took quite some hours before I understood it wasn't 
going to help with what I was coding in my application.

Matthew.

On Mon, Feb 16, 2015 at 04:22:25AM -0800, harshavardhan Reddy wrote:
> Hi All,
> 
> Is ntop DPI integration available for Intel DPDK..?
> 
> I could see only Propretory qosmos ixEngine integrated with DPDK and
> Windriver with its own DPI.
> 
> But not found any info about nDPI integration with DPDK.
> 
> 
> Thank You,
> 
> Regards,
> HVR

      reply	other threads:[~2015-02-17  0:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 12:22 harshavardhan Reddy
2015-02-17  0:58 ` 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=20150217005805.GA30617@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=hvreddy1110@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;
as well as URLs for NNTP newsgroup(s).