On Fri, Feb 1, 2013 at 3:57 PM, Ravi Kumar Tenneti <[email protected]> wrote: > We have tried the following with mixed results : > > 1. Squid with delay pools - download limits are working but uploads > limitation is not working.
One aspect that is most often missed is that traffic shaping using which QoS is delivered is effective for outgoing traffic but is not effective for incoming traffic on an interface. Ingress qdiscs also fail miserably in a NAT scenario where the incoming traffic is all destined to the gateway and the destination nodes are unknown till after reverse NAT rewrites of the packet (happens post where Ingress qdiscs are applied). The method that I found that works well for controlling both ingress and egress traffic to the internet is to: (a) Configure the gateway as a bridged/transparent gateway (both interfaces in the same subnet with forwarding of traffic from one interface to another). No reconfiguring of the network is needed (bump in the wire scenario). (b) Apply egress qdiscs on the internet facing interface to shape outgoing traffic. (c) Apply egress qdiscs on the LAN facing interface to shape incoming traffic from the internet. Howtos exist for this. I wrote and maintained user documentation chapters for bridging[1] and bridged QoS[2] for an embedded linux distro called LEAF (it has been static for a long time now :( ). Other good ones exists especially in LARTC though they are more generic. Links: [1] http://leaf.sourceforge.net/doc/bubridge.html [2] http://leaf.sourceforge.net/doc/buhtb-qos.html -- Mohan Sundaram _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
