All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Weingart <lartc@pentax.boerde.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Intelligent P2P detection
Date: Tue, 25 Mar 2003 12:44:52 +0000	[thread overview]
Message-ID: <marc-lartc-104859642830245@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104857984213566@msgid-missing>

On Tue, Mar 25, 2003 at 11:21:34AM +0100, Kim Jensen wrote:

> 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 

This does not help, because often they use port 80 or 25 or so. But e-mule
is using some fixed ports (4426 or similar?) as control connection (like
passive ftp). A module that is analysing that control traffic (similar to
ftp) and determine the ports that are then used by the transfer connections
should be able to mark all e-mule packets; but I have not seen a
implementation of this yet. However there are sources of P2P servers/clients
available, and it should be possible to implement such a tool or I should
better say different tools for different P2P-software ;-(. (and maybe not
for all kind of that software).  I agree with you, it would be fine to have
such a tool.

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

  parent reply	other threads:[~2003-03-25 12:44 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
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 [this message]
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-104859642830245@msgid-missing \
    --to=lartc@pentax.boerde.de \
    --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.