From: Eliezer Croitoru <eliezer@ngtech.co.il>
To: Lutfi ODUNCUOGLU <lutfio@metu.edu.tr>
Cc: ntop-dev@unipi.it, Ed W <lists@wildgooses.com>,
netfilter@vger.kernel.org
Subject: Re: [Ntop-dev] New/Updated L7 netfilter option - nDPI
Date: Tue, 06 Nov 2012 16:13:06 +0200 [thread overview]
Message-ID: <50991AF2.30107@ngtech.co.il> (raw)
In-Reply-To: <5093BEAB.2040002@metu.edu.tr>
On 11/2/2012 2:38 PM, Lutfi ODUNCUOGLU wrote:
> Hello,
>
> I compiled nDPI-nefilter patch and it works fine. What I want is to
> shape the p2p traffic in my network. For this purpose i just implemented
> the nDPI-netfilter patch as two different ways for testing
>
> iptables -t mangle -A POSTROUTING -o XXX -m ndpi --bittorrent -j
> CONNMARK --set-mark 1
>
>
> iptables -t mangle -A POSTROUTING -m connmark --mark 1 -j CLASSIFY
> --set-class 0001:0010
>
> or
>
> iptables -t mangle -A POSTROUTING -m ndpi --bittorrent -j CLASSIFY
> --set-class 0001:0010
>
>
> So which one is more suitable for use? I don't know if this patch
> inspects connections (marks connection) or every single packet (marks
> every single) for a match.
>
>
> Regards,
>
> Lutfi
Hey Lutfi,
it seems to me that the set-mark is used more then classify and from
ndpi point of view it's better then restoring marks etc since ndpi
stores the connection status.
Regards,
Eliezer
--
Eliezer Croitoru
https://www1.ngtech.co.il
IT consulting for Nonprofit organizations
eliezer <at> ngtech.co.il
next prev parent reply other threads:[~2012-11-06 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 22:53 New/Updated L7 netfilter option - nDPI Ed W
2012-10-28 8:20 ` 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 ` Eliezer Croitoru [this message]
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=50991AF2.30107@ngtech.co.il \
--to=eliezer@ngtech.co.il \
--cc=lists@wildgooses.com \
--cc=lutfio@metu.edu.tr \
--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.