From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Furniss Date: Thu, 18 Nov 2004 14:15:32 +0000 Subject: Re: [LARTC] Bandwidth throttling/limiting for all traffic Message-Id: <419CAE84.6040207@dsl.pipex.com> List-Id: References: <419C172A.2050009@ascend.net.au> In-Reply-To: <419C172A.2050009@ascend.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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/