From: Jandre Olivier <jandre@megaserve.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Matching with Layer7 vs. IPP2P
Date: Wed, 19 Apr 2006 07:35:37 +0000 [thread overview]
Message-ID: <4445E849.1040608@megaserve.net> (raw)
In-Reply-To: <e23tr3$ce3$1@sea.gmane.org>
I was just about to post the same post,
I currently use ipp2p and it works pretty well, It just doesnt seem to
track morpheous(fasttrack) protocols, otherwise it works pretty well. I
have quite alot of connections and havent seen any performance issues.
My next step is to add L7 as well with ipp2p to completely block/shape p2p.
However I find L7 bit more tricky than ipp2p to compile
Cannot comment on L7
J
Arik Raffael Funke wrote:
> Hi,
>
> can anybody comment on the cost of matching with IPP2P vs. Layer7.
>
> Also, does a iptables rule with more complicated matching mechanism also
> slow down processing if all the packets are matched before they reach
> the rule. I.e. is the mere existence of a potentially costly rule
> already slowing down processing or only if packets are actually
> processed by it?
>
> Thanks very much in advance.
>
> Best regards,
> Arik
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
/*---------------------------------------------------------------------*/
__ _
---------- / / (_)__ __ ____ __ ---------
------- / /__/ / _ \/ // /\ \/ / --------
---- /____/_/_//_/\_,_/ /_/\_\ ------
localhost@localdomain.za.net
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-19 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 23:47 [LARTC] Matching with Layer7 vs. IPP2P Arik Raffael Funke
2006-04-19 7:35 ` Jandre Olivier [this message]
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=4445E849.1040608@megaserve.net \
--to=jandre@megaserve.net \
--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.