From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Unterkircher Date: Sun, 11 Dec 2005 17:12:59 +0000 Subject: Re: [LARTC] shareaza Message-Id: <439C5E1B.3090205@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'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). ncrfgs schrieb: > On Sun, Dec 11, 2005 at 05:30:55PM +0200, Georgi Alexandrov wrote: > >>> If B uploads a file to C through gnutella everything works >>> like a charm since packets look just like this: >>> >>> 192.168.0.2:6346 > xxx.xxx.xxx.xxx:yyyyy >>> >>> With tc I filter packets whose source port is 6346 and >>> everything is fine. >>> >> You can classify the traffic from B going out trough ppp0 with >> netfilter/iptables like this: >> > > What you wrote is indeed very similar to what I use right > now except for the fact that I'm classifying according to > the source port, too. > > The side effect of your configuration is that all of the > traffic from B though ppp0 is shaped. The configuration > you've suggested is interesting but I'd like to limit the > shareaza traffic only. > > Is there any way to do that? How can I keep track of the > traffic generated by shareaza only? > > > > 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