From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shareaza
Date: Sun, 11 Dec 2005 20:03:56 +0000 [thread overview]
Message-ID: <439C862C.9090706@gmail.com> (raw)
In-Reply-To: <20051211144541.GA4079@ncrfgs3.ncrfgs>
ncrfgs wrote:
>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.
>
>
Perhaps you need something like l7-filter.sf.net ?
Georgi Alexandrov
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-12-11 20:03 UTC|newest]
Thread overview: 10+ 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:14 ` Georgi Alexandrov
2005-12-11 18:26 ` Leonardo Rodrigues Magalhães
2005-12-11 20:13 ` Georgi Alexandrov
2005-12-11 17:12 ` Andreas Unterkircher
2005-12-11 17:49 ` ncrfgs
2005-12-11 18:45 ` Andreas Unterkircher
2005-12-11 20:03 ` Georgi Alexandrov [this message]
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=439C862C.9090706@gmail.com \
--to=georgi.alexandrov@gmail.com \
--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.