>On Thursday 31 July 2003 10:00, Martin A. Brown wrote: >> Well....(you'll love this) the reason everyone is saying "you can't shape >> incoming traffic" is because you can't shape incoming traffic (withoutswift-online >> IMQ). > >Well, i shape incoming traffic without IMQ (: >I made my bandwidth.manager is on top of every router in my organization, so >every traffic coming or leaving my organization must be processed by my >bandwidth.manager first.. > >> Well, in short, what we're really saying is that you can't control what >> you receive (without IMQ). As the recipient of frames/packets, you have >> no control over how fast they arrive in your device's input queue. > >In my bandwidth.manager eth0 would be upgoing packet that needs to be manage, >while eth1 would be the incoming packet to my LAN network. In the absence of IMQ, this is what is recommended. Use ingress police to cap overall incoming bandwidth and use qdiscs on LAN interface to shape traffic. However, in cases like ISPs and a few corporate scenarios, the requirement is to throttle/manage bandwith for incoming and outgoing traffic e.g. 64kbps incoming+outgoing for an IP. In your scenarion, incoming and outgoing are capped/managed separately but they cannot borrow from each other as they are on different interfaces. IMQ being a single interface for both incoming and outgoing allows this. > >Regards, >Rio Martin. >-- >Game of love, we play, we win only to loose. > >_______________________________________________ >LARTC mailing list / LARTC@xxxxxxxxxxxxxxx >http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > Mohan
