All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Scalability
Date: Wed, 29 Sep 2004 10:13:20 +0000	[thread overview]
Message-ID: <3063e50409290313b61b303@mail.gmail.com> (raw)

Hello everyone,


I want an opinion from people who tryed different matching modules to
match diferent types of traffic, especially p2p ones.
I would like to hear which scales better as CPU usage and latency :
ipp2p, iptables-p2p or l7-filter with the p2p patterns. I want to use
one of them to block most of p2p (except maybe dc++ and emule which i
want to shape). I would use the matching rules in mangle table, i hope
there is a way not to make the entire traffic matching the rules.
After i mark such traffic, i want to use connmark to mark the entire
stream and then to change the mark based on ip of every LAN client.
Perhaps a tweak would be to send 0x0 marked traffic to a chain and
apply such matches there, so really few traffic will  go to p2p
matching. Everything you people will tell me are very apreciated, i
wil probably begin working on this on a server from now in some days.

Thanks in advance.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-09-29 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 10:13 George Alexandru Dragoi [this message]
2004-09-29 14:42 ` [LARTC] Scalability Andreas Klauer
2004-09-30 12:42 ` George Alexandru Dragoi
2004-09-30 13:00 ` Andreas Klauer
2004-09-30 14:11 ` George Alexandru Dragoi

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=3063e50409290313b61b303@mail.gmail.com \
    --to=waruiinu@gmail.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.