From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shareaza
Date: Sun, 11 Dec 2005 18:45:44 +0000 [thread overview]
Message-ID: <439C73D8.7060503@netshadow.at> (raw)
In-Reply-To: <20051211144541.GA4079@ncrfgs3.ncrfgs>
I guess it's not possible without knowing the nature of these protocols.
It's like the ftp-data
channel... without looking into the ftp-cmd channel (ip_conntrack_ftp)
iptables wouldn't
know that the two connections are related...
ncrfgs schrieb:
> On Sun, Dec 11, 2005 at 06:12:59PM +0100, Andreas Unterkircher wrote:
>
>> I'm not very familar with all these p2p protocols. But
>> isn't shareaza supporting all the other p2p protocols?
>> Like edonkey and bittorrent...
>> Most of them can be matched with ipp2p (www.ipp2p.org)
>> or l7-filter (l7-filter.sf.net).
>>
>
> As far as I know they can but I wondered whether it was
> possible to accomplish the task using only vanilla iptables
> and iproute.
>
> It looks like it works like this: shareaza ``negotiate''
> with the other end listening on port 6346, then they try to
> ``find an agreement'' about which other port to use and in
> the end uploads actually occurs on that one. Am I right?
>
> Generally speaking, how can I recognize and keep track of
> edonkey connections?
>
>
>
> Thanks in advance.
>
> Best regards.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-11 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 14:45 [LARTC] shareaza ncrfgs
2005-12-11 15:30 ` Georgi Alexandrov
2005-12-11 17:00 ` ncrfgs
2005-12-11 17:12 ` Andreas Unterkircher
2005-12-11 17:49 ` ncrfgs
2005-12-11 18:45 ` Andreas Unterkircher [this message]
2005-12-11 20:03 ` Georgi Alexandrov
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=439C73D8.7060503@netshadow.at \
--to=unki@netshadow.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox