HI there Simple question :-) Why there is always only qos examples for upload and not download stream of adsl? 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. Now comes the filtering and I was wondering if there 1. makes sense i.e. it helps us if download speed is at limit to priorize ssh, voip etc. 2. what will be the cpu load if you have not only 5 connected clients if not say 30 and a lot of filter rules i.e. each customer needs his full filter set ... Has anybody such a thing in production or is it "useless"? Greetings Beat
Hi, Beat Meier wrote:> HI there > > Simple question :-) > Why there is always only qos examples for upload and not download stream of > adsl?The packages are allready on your router, so why slowing down the routing? You cannot hinder anyone to send you data but you can control the questioning for more incoming traffic. (the case here is a "slow" internet connection) [...]> > Now comes the filtering and I was wondering if there > 1. makes sense i.e. it helps us if download speed is at limit to priorize > ssh, voip etc. > 2. what will be the cpu load if you have not only 5 connected clients if > not say 30 > and a lot of filter rules i.e. each customer needs his full filter set ...[...] That''s how I would argue on the other questions with a "no". (Btw., afaik the traffic of 5 or 30 people would not fully load a 200MHz mipsel router on this line, but effectively shaping for low latency (voip) could be hard to deal with on that line). Bye, Andreas.
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