From: Ed W <lists@wildgooses.com>
To: netfilter@vger.kernel.org, ntop-dev@unipi.it
Cc: "G. Elian Gidoni" <geg@gnu.org>
Subject: New/Updated L7 netfilter option - nDPI
Date: Wed, 24 Oct 2012 23:53:47 +0100 [thread overview]
Message-ID: <5088717B.6080300@wildgooses.com> (raw)
Hi all. There is an interesting project that was called opendpi
(originally by ipoque GmbH) and recently been forked and maintained by
the ntop guys under the nDPI label. It offers a new and currently
maintained layer 7 (L7) packet identification library. It could
definitely benefit from more eyes and development effort, but at present
it gives much better breakdown of traffic for ntop
There is a netfilter library, originally by Elian Gidoni, that I have
updated to use the nDPI fork
https://github.com/ewildgoose/ndpi-netfilter
The practical upshot is that you can do stuff like:
iptables -I FORWARD -m opendpi --WinUpdate -j LOG
or
iptables -I FORWARD -m opendpi --skype -j REJECT
In theory you can also filter Facebook, Twitter, etc, but I concede that
doesn't seem to work as expected right now...
Another of the clever things that nDPI does is to try and classify SSL
traffic by examining the name on the cert. A technique that seems
likely to allow crude identification of significant traffic.
We could benefit from more eyes on this, both the netfilter module and
the nDPI library
Thanks for your feedback
Ed W
next reply other threads:[~2012-10-24 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 22:53 Ed W [this message]
2012-10-28 8:20 ` New/Updated L7 netfilter option - nDPI Andrew Beverley
2012-10-28 14:57 ` Eliezer Croitoru
2012-11-01 22:03 ` Andrew Beverley
2012-11-01 22:56 ` Ed W
2012-11-02 12:38 ` Lutfi ODUNCUOGLU
2012-11-02 13:40 ` Ed W
2012-11-06 14:13 ` [Ntop-dev] " Eliezer Croitoru
2012-11-04 15:45 ` Andrew Beverley
2012-10-28 16:34 ` Ed W
2012-10-28 16:39 ` Eliezer Croitoru
2012-10-28 15:07 ` Eliezer Croitoru
2012-10-28 16:03 ` Ed W
2012-10-28 16:51 ` Eliezer Croitoru
2012-10-28 16:57 ` Ed W
2012-10-28 17:57 ` Eliezer Croitoru
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=5088717B.6080300@wildgooses.com \
--to=lists@wildgooses.com \
--cc=geg@gnu.org \
--cc=netfilter@vger.kernel.org \
--cc=ntop-dev@unipi.it \
/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.