All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Detecting p2p traffic
Date: Mon, 22 May 2006 06:26:35 +0000	[thread overview]
Message-ID: <4471599B.1080102@andybev.com> (raw)
In-Reply-To: <20060508004307.qkuxq25v4occs4gk@www.simplelists.com>

Jason Boxman wrote:
> On Sunday 07 May 2006 19:43, Andrew Beverley wrote:
>> After varying degrees of success with p2p detection modules, I would like
>> to write the following rules using iptables to reliably identify p2p
>> traffic:
>>
> <snip>
>> On my network all p2p traffic falls into these categories, and I don't mind
>> overmatching with other traffic.
> 
> If you can, you could look into compiling and using ipp2p against your kernel.  
> I find it works extremely well with my p2p traffic from edonkey protocol(s).  
> You may have success with L7-Filter, too.  You can probably use both at the 
> same time, but I've never tried as ipp2p works for me.

Thanks - I tried both ipp2p and l7-filter. I found that on the whole 
they worked well, but on the network of 50 clients there was always a 
couple that it didn't detect. I also wanted to put something in place 
that didn't need upgrading - if and when I move on someone will have to 
keep updating ipp2p and l7-filter on the server.

Andy


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-05-22  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 23:43 [LARTC] Detecting p2p traffic Andrew Beverley
2006-05-08 19:22 ` Jason Boxman
2006-05-22  6:26 ` Andrew Beverley [this message]
2006-05-22  6:39 ` Andrew Beverley
2006-05-22  6:42 ` Samuel Díaz García
2006-05-22 14:25 ` Luciano Ruete

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=4471599B.1080102@andybev.com \
    --to=andy@andybev.com \
    --cc=lartc@vger.kernel.org \
    /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.