All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lutfi ODUNCUOGLU <lutfio@metu.edu.tr>
To: ntop-dev@unipi.it
Cc: Eliezer Croitoru <eliezer@ngtech.co.il>, netfilter@vger.kernel.org
Subject: Re: New/Updated L7 netfilter  option - nDPI
Date: Fri, 02 Nov 2012 14:38:03 +0200	[thread overview]
Message-ID: <5093BEAB.2040002@metu.edu.tr> (raw)
In-Reply-To: <5092FE2D.40009@wildgooses.com>

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


On 11/02/2012 12:56 AM, Ed W wrote:
> On 01/11/2012 22:03, Andrew Beverley wrote:
>> On Sun, 2012-10-28 at 16:57 +0200, Eliezer Croitoru wrote:
>>>> I have to admit that I only had limited success with l7-filter,
>>>> although
>>>> it no longer appears to be maintained anyway.
>>>>
>>> What would you want to achieve from a using l7 iptables?
>>> filtering? scheduling?
>> At the time I was using it to do traffic shaping, to prevent p2p
>> applications overloading a network with low bandwidth internet
>> connection. The problem was that it only needed one p2p application to
>> not be identified for the network to be overloaded. So in the end I took
>> a rather rudimentary approach and just identified any client making lots
>> of connections to ports above 1024:
>>
>> http://www.andybev.com/index.php/Fair_traffic_shaping_an_ADSL_line_for_a_local_network_using_Linux
>>
>>
>>
>
>
> I think it's safe to assume that at least a determined attacker can
> avoid these filters. Ideally you want them reasonably accurate for the
> normal situation...
>
> I guess you just invented an "L7 Filter" yourself... It's just as good a
> match for certain requirements...!
>
> Let me know if you measure this thing against your problem?
>
> Cheers
>
> Ed W
> _______________________________________________
> Ntop-dev mailing list
> Ntop-dev@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-dev

  reply	other threads:[~2012-11-02 12:38 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 [this message]
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=5093BEAB.2040002@metu.edu.tr \
    --to=lutfio@metu.edu.tr \
    --cc=eliezer@ngtech.co.il \
    --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.