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] Bandwidth throttling/limiting for all traffic
Date: Thu, 18 Nov 2004 14:15:32 +0000	[thread overview]
Message-ID: <419CAE84.6040207@dsl.pipex.com> (raw)
In-Reply-To: <419C172A.2050009@ascend.net.au>

Darryl Cording wrote:
> Darryl Cording wrote:
> 
>>
>> But it seems my ftp transfers are not being shaped, in fact, lol, they 
>> are going faster from when I first started experimenting. So it's not 
>> matching correctly. I just want to shape everything going past the 
>> NIC's. I thought that if I could classify the entire ip protocol or 
>> the tcp protocol that would shape the bulk of the traffic ?  I was 
>> hoping not having to get down to specifying ports, but find a simple 
>> way to shape all outgoing traffic on a multi-homed host.
>>
>> Am I on the right track?
>>
> I guess I could match by ip addresses but I hoping for a simpler way to 
> match everthing.

You were close - default refers to the number after the :

10: is short for  10:0 .

tc qdisc add dev eth0 root handle 10: htb default 1
tc class add dev eth0 parent 10: classid 10:1 htb rate 64kbit ceil 64kbit

should shape everything.

Andy.

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

  parent reply	other threads:[~2004-11-18 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18  3:29 [LARTC] Bandwidth throttling/limiting for all traffic Darryl Cording
2004-11-18  5:09 ` Jason Boxman
2004-11-18  6:20 ` Darryl Cording
2004-11-18 13:22 ` Darryl Cording
2004-11-18 13:50 ` Darryl Cording
2004-11-18 14:15 ` Andy Furniss [this message]
2004-11-18 20:09 ` Darryl Cording

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=419CAE84.6040207@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.