All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shared ADSL SHAPER
Date: Sat, 25 Feb 2006 15:01:02 +0000	[thread overview]
Message-ID: <4400712E.5060307@dsl.pipex.com> (raw)

Rasmus Melgaard wrote:
> Hi,
> 
> I'm trying to make a shaper / firewall to improve sharing of bandwidth on a 
> ADSL (3mbit down / ½ mbit up)
> 
> Since the ADSL is very asymmetric, down is unimportant, I make a ingress rate 
> limit shaper to ensure, all shaping is at the Shaper, and not on the Router 
> or the ISP.
> 
> The Idea is then to make one HTB hierarchy and have each client (IP) filtererd 
> and put in a child-HTB queue. This is the main idea, I have added prio to 
> each HTB-child to keep priorities for each client.
> 
> I currently use a reduced setup with total-uplink limited to 160kbit, and i 
> run first the firewall script (first) and then the Shaper script, below.
> 
> The problem is know that if a take Azureus, bittorrent client, and let it go 
> (no uplink limitation), it now kills its own downlink speed. If I limit the 
> uplink speed in Azureus the downlink will grow again, it is quiet obvious. 
> 
> I've tried adding some trick from the net, to especially improve ACK 
> performance, but it hasn't helped.

I haven't checked the script but assuming it's OK I think that this 
could be fixed - I use the python client and it seems OK.

When you back off you will get fairness from the client - so you should 
use sfq.

You will need to priorotise small packets - I use < 128.

You also need to limit the length of the sfq to say 20 - 30 so that you 
get plenty of drops and less acks for the download get piggybacked on 
the upload packets - bittorrent uses tcp full duplex which makes it a 
bit of a special case for shaping.

Always remember that unless you patch/use overhead parameters that you 
need to back off from the advertises link rate.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-02-25 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 15:01 Andy Furniss [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-30 17:45 [LARTC] Shared ADSL SHAPER Rasmus Melgaard

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=4400712E.5060307@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 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.