From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Unterkircher Date: Sun, 11 Dec 2005 18:45:44 +0000 Subject: Re: [LARTC] shareaza Message-Id: <439C73D8.7060503@netshadow.at> List-Id: References: <20051211144541.GA4079@ncrfgs3.ncrfgs> In-Reply-To: <20051211144541.GA4079@ncrfgs3.ncrfgs> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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