All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Jensen <kimj@dawn.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Intelligent P2P detection
Date: Tue, 25 Mar 2003 10:21:34 +0000	[thread overview]
Message-ID: <marc-lartc-104858770421891@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104857984213566@msgid-missing>

Hi Luman,

Sorry, I have a stupid question - why do you wish to mark the traffic, is it 
because you wish to allow it internally or is it because you wish to 
completely drop it?

If you wish to mark it, then I can recommend that you take a look at the 
patch-o-matic module connmark. All packets destined for your internal 
services or external services where the destination port is above 1024 can 
then easily be marked and tracked (at least in theory, I haven't played with 
the connmark module yet).

/Kim

On Tuesday 25 March 2003 09:08, Luman wrote:
> Probably, I'm not the first one who needs solve problem with p2p.
> Because, large part of my traffic is eaten by p2p software like KazAA,
> e-mule, Direct Connect etc, I'm looking for the way of detection of such
> traffic and marking it. However simple way with for instance 1214 port
> for KazAA doesn't work because this software uses floating port
> technology. This traffic can be send via different ports and these ports
> can change in the fly. This is rather well known.
> So I'm looking for the stuff working at higher level and analyzing
> traffic inside to determine the content and the real protocol. It could
> be a patch to the kernel or whatever. It should only be able to mark
> packet by a special marker.
>
> I need this solution not only to prioritizing the traffic (prioritizing
> can be achieve in other way) but also to selection the Internet link. I
> want to NAT this low quality data for some specific address in order to
> send it over cheaper link.
>
> What do you think is there any solution to do it? Or maybe there is
> ongoing project trying to tackle with this global problem with detection
> p2p traffic.
>
> Best regards,
> Luman
>
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

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

  reply	other threads:[~2003-03-25 10:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  8:08 [LARTC] Intelligent P2P detection Luman
2003-03-25 10:21 ` Kim Jensen [this message]
2003-03-25 10:53 ` Luman
2003-03-25 12:20 ` Kim Jensen
2003-03-25 12:24 ` Luman
2003-03-25 12:30 ` Luman
2003-03-25 12:44 ` Matthias Weingart
2003-03-25 12:51 ` Robert Kryczało
2003-03-25 12:56 ` Luman
2003-03-25 13:05 ` Robert Kryczało
2003-03-25 15:27 ` Robert Kryczało
2003-03-26 21:37 ` Dawid Kuroczko
2003-03-26 21:50 ` Dawid Kuroczko
2003-03-27  9:24 ` Luman
2003-03-27  9:35 ` Luman
2003-03-27 10:16 ` Gordan Bobic
2003-03-27 15:20 ` Robert Kryczalo
2003-03-27 15:32 ` Robert Kryczało
2003-03-27 16:04 ` Gordan Bobic
2003-03-27 16:38 ` Robert Kryczało
2003-03-27 16:43 ` Gordan Bobic
2003-03-27 20:15 ` Matthias Weingart
2003-03-27 21:34 ` Arvid Stüwe
2003-03-28  8:14 ` Robert Kryczało
2003-03-31 12:10 ` Szymon Miotk
2003-03-31 12:32 ` Patrick McHardy

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=marc-lartc-104858770421891@msgid-missing \
    --to=kimj@dawn.dk \
    --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.