From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andy Furniss <andy.furniss@dsl.pipex.com>
Date: Mon, 14 Nov 2005 22:36:08 +0000
Subject: Re: [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design
Message-Id: <43791158.9060501@dsl.pipex.com>
List-Id: <lartc.vger.kernel.org>
References: <BF782D07436CAE4B931BFA5B2C68FF4F0F8B9E@bmts1.ad.bmtseatech.co.uk>
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8B9E@bmts1.ad.bmtseatech.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Mark Lidstone wrote:
> Hi Andy,
> 
> Many thanks for the reply.
> 
> Is there a reason why the user is not supposed to use pfifo_fast?  I
> don't think I need a full-on PRIO (surely pfifo_fast is more efficient
> if it is classless?).  Sorry for asking, but I didn't come across this
> limitation in the documentation.

Not sure really.

> 
> Following your suggestions, I've come up with the following:
> 
> 	#!/bin/sh
> 	SQ="tc qdisc add dev eth0"
> 	SC="tc class add dev eth0"
> 	SF="tc filter add dev eth0"
> 	
> 	tc qdisc del dev eth0 root
> 	$SQ root handle 1:0 htb
> 	$SC parent 1:0 classid 1:1 htb rate 4096kbit
> 	$SC parent 1:1 classid 1:2 htb prio 0 rate 768kbit #Video
> Conferencing
> 	$SC parent 1:1 classid 1:3 htb prio 1 rate 1545kbit #Company 1
> 	$SC parent 1:1 classid 1:4 htb prio 1 rate 832kbit #Company 2
> 	$SC parent 1:1 classid 1:5 htb prio 1 rate 713kbit #Company 3
> 	$SC parent 1:1 classid 1:6 htb prio 1 rate 238kbit #Company 4
> 	$SQ parent 1:2 handle 5:0 prio #Video Conferencing
> 	$SQ parent 1:3 handle 6:0 prio #Company 1
> 	$SQ parent 1:4 handle 7:0 prio #Company 2
> 	$SQ parent 1:5 handle 8:0 prio #Company 3
> 	$SQ parent 1:6 handle 9:0 prio #Company 4
> 	
> 	$SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.4/32
> flowid 5:0
> 	$SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.5/32
> flowid 6:0
> 	$SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.6/32
> flowid 7:0
> 	$SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.7/32
> flowid 8:0
> 	$SF parent 1:0 protocol ip prio 0 u32 match ip src 1.2.3.8/32
> flowid 9:0
> 
> (I've a horrible feeling there's something obviously and fundamentally
> wrong with this)
> 
> What happens with any traffic not from these IPs?

You can use a catch all filter after the others ... u32 match u32 0 0 ..

Unlike htb prio 1 is the top prio for filters.

Without knowing what your setup is it's hard to say what's the best way 
in detail eg. where and what bandwidth are the bottleneck links and 
which end of them you are shaping.

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