From: Andrew Beverley <andy@andybev.com>
To: Eliezer Croitoru <eliezer@ngtech.co.il>
Cc: Ed W <lists@wildgooses.com>,
netfilter@vger.kernel.org, ntop-dev@unipi.it,
"G. Elian Gidoni" <geg@gnu.org>
Subject: Re: New/Updated L7 netfilter option - nDPI
Date: Thu, 01 Nov 2012 22:03:02 +0000 [thread overview]
Message-ID: <1351807382.2243.51.camel@andylaptop> (raw)
In-Reply-To: <508D47E2.8020800@ngtech.co.il>
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
Andy
next prev parent reply other threads:[~2012-11-01 22:03 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 [this message]
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=1351807382.2243.51.camel@andylaptop \
--to=andy@andybev.com \
--cc=eliezer@ngtech.co.il \
--cc=geg@gnu.org \
--cc=lists@wildgooses.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox