From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Scalability
Date: Thu, 30 Sep 2004 14:11:52 +0000 [thread overview]
Message-ID: <3063e5040930071119ef2975@mail.gmail.com> (raw)
In-Reply-To: <3063e50409290313b61b303@mail.gmail.com>
My intension is of course to match p2p first, then others. I realised
i must be more carefully with marks, since it does not get marked
from first packets. I belive some sort of masks applyed to marks are
necesary, the p2p should begin all with, let's say 0x2 then 3 hex
"digits" so i can distinguish non p2p for other purpose later. Is it
possible better ? (i bet it does).
On Thu, 30 Sep 2004 15:00:39 +0200, Andreas Klauer
<andreas.klauer@metamorpher.de> wrote:
> Am Thursday 30 September 2004 14:42 schrieb George Alexandru Dragoi:
> > Such traffic will be matched agains src ip or dest ip, or port number
>
> If you can use these kinds of optimizations, then that's fine.
> In my case, P2P applications can run on any port and any IP,
> so it's not possible for me. If I added a filter rule like that,
> chances are good that clients would find out and use these ports
> for their P2P applications.
>
> Andreas
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-09-30 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 10:13 [LARTC] Scalability George Alexandru Dragoi
2004-09-29 14:42 ` 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 [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=3063e5040930071119ef2975@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.