Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] noprioportsrc
Date: Sun, 11 Apr 2004 22:31:55 +0000	[thread overview]
Message-ID: <4079C75B.403@dsl.pipex.com> (raw)
In-Reply-To: <200403291208.12134.finbert@sbcglobal.net>

Richard wrote:
> On Monday 29 March 2004 11:15 pm, Damion de Soto wrote:
> 
> 
>>I've fonud trying to make
>>bittorrent behave itself is quite difficult.
>>The 3 classes have rates specified as UPLINK, 9*$UPLINK/10 and 8*$UPLINK/10
>>This means the sum of the 3 classes is greater than the parent.
>>You may want to specify the rates as something lower that add up to UPLINK,
>>and then specify the ceil value for each class.
> 
> 
> I tried what you had suggested and I was able to get great pings while 
> uploading using the script!
> 
> Now this is the really things get strange.  Without doing anything to my 
> connection or with wondershaper, about after 1 hour of running the script 
> (and having my bandwith limited to 50kb/s) something changes and I start 
> uploading at my max again.
> 
> Why is this happening?

I don't think marking those BT ports will catch all BT connections - BT 
will work without opening ports. I think you can mark with one of the 
P2P marking projects on sf.net.

Andy.



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

      parent reply	other threads:[~2004-04-11 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 12:08 [LARTC] noprioportsrc Richard
2004-03-29 21:31 ` Richard
2004-03-29 23:15 ` Damion de Soto
2004-04-11 22:31 ` Andy Furniss [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=4079C75B.403@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox