From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mohan Sundaram Date: Sat, 13 Oct 2007 02:58:55 +0000 Subject: Re: [LARTC] Why not qos for downloading stream?? Message-Id: <4710319F.2070201@vsnl.com> List-Id: References: <470FEA9F.6020707@swiss-wireless.com.ar> In-Reply-To: <470FEA9F.6020707@swiss-wireless.com.ar> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Beat Meier wrote: > HI there > > Simple question :-) > Why there is always only qos examples for upload and not download stream > of adsl? QoS works on packet queuing at the interface level. We can only queue what we send out or police/ rate limit what you receive. On edge devices, normally, a incoming stream on one interface translates to one or more outgoing streams on other interfaces. Thus applying QoS on an egress interface is equivalent to doing QoS on the ingress interface. TCP/IP slows down automatically when some congestions occur. The above does not hold true for UDP/ICMP and that is why these are commonly rate limited at ingress. > I have a linux router which shares 5 wireless "customers" my neighbours > and me to > one adsl link 512kbps download 128kbps upload ... > Now does it make sense to do qos on the linux router for download for us? > Say if someone is using ssh from outside ... > So I tried to apply the example 15.10 of Cookbook of the lartc howto on > the linux router ... > I have for every neighbour a class which limits its traffic to 128kbps > and below that > I addedd the whole tree of example 15.10 on the router ... > Or does it make more sense this to do on the ap with ingress? I have a > full linux > ap router for each neighbour. > Shape outgoing traffic on the interface that faces each customer. Mohan _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc