Thanks Mohammed. If we are using the LEAF box as a bridge, then shaping on a device will shape all packets. E.g. Let us say eth0 is external on 10.0.0.1 and eth1 is internal 10.0.0.2. Then packets coming to the 10.x.x.x network from the router will come to the LEAF box and go out on both eth0 and eth1. If traffic shaping is applied in eth0, then even this traffic will be shaped thus unneccesarily eating bandwidth.
Am I right or am I wrong? I saw a howto on briging on linux and it talks about a device br0. Is this like imq? Will shaping on this device shape both incoming and outgoing traffic or only oneway i.e. eth0 to eth1 or vice-versa? Are there any specific configurations needed for bridge.lrp? If not, I wonder why we have howtos on bridging in Linux and devices like br0. Can someone throw some light please? Mohan P.S: Dear Mohammed - English is a language. Not being very good at it does not affect our primary purpose of sharing knowledge. Please do not be apologetic on this front. -----Original Message----- From: Muhammad Wicaksono Mursid [mailto:m_wicaksono_m@;yahoo.com] Sent: Tuesday, November 12, 2002 12:19 AM To: S Mohan Subject: Re: [leaf-user] bandwidth management. Hello mohan, i'll help u Sorry if my english is not good. You must download modules to support HTB, TBF and SFQ for TC support and put them in /lib/modules : I don't know which one is used or not used, but i put them in to /lib/modules and declare all of that to packages configuration to load ad boot. So with this command, (HTB) i use it : # TC Rules for htb with sfq (downstream) tc qdisc add dev eth1 root handle 1: htb default 13 tc class add dev eth1 parent 1: classid 1:1 htb rate 160Kbit ceil 160Kbit tc class add dev eth1 parent 1:1 classid 1:11 htb rate 32Kbit ceil 64Kbit tc class add dev eth1 parent 1:1 classid 1:12 htb rate 64Kbit ceil 128Kbit tc class add dev eth1 parent 1:1 classid 1:13 htb rate 160Kbit ceil 160Kbit tc qdisc add dev eth1 parent 1:11 handle 11: sfq perturb 10 tc qdisc add dev eth1 parent 1:12 handle 12: sfq perturb 10 tc qdisc add dev eth1 parent 1:13 handle 13: sfq perturb 10 tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32 match ip dst 202.51.233.116 flowid 1:11 tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32 match ip dst 202.51.233.115 flowid 1:12 I run it in bering bridge box, an put them all to /etc/init.d/bootmisc.sh Thank's __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
