Am I correct in assuming that you only need to use the Ingres qdisc if you're not the router between two networks (namely the internet and your customers). We have CBQ/TBF setup for our incoming traffic (internet to customer). Can the same rules be applied in reverse for outgoing traffic (customer to internet)? Thanks, Kristian Hoffmann PC-InTOUCH/FireToWire System Administrator khoff@xxxxxxxxxxxxxx --- On Sun, 18 Nov 2001, Martin Devera wrote: > It is nerly FAQ. You can use Ingres qdisc to do it and attach > policers here. > It would be nice to be able to attach every qdisc to incoming interface > but it is not possible. There is always problem - when packet already > hitted your box why do you want to drop/delay it ? > You should to do it on outgoing side of link to your box .. > > When you are router (not app box) then you can shape both directions. > On your virtual-host note. I already did patch (called IMQ) which > implements virtual inteface allowing to attach single qdisc to multiple > outgoing devices. > It should be relatively easy to extend it to catch incoming packets > too - only there is no time to do it. > > best regards, devik > > On 19 Nov 2001, Manfred Bartz wrote: > > > > > I would like to differentiate incoming traffic streams to guarantee > > minimum bandwidth to some services. However, as per the > > Adv-Routing-HOWTO it appears that only outgoing traffic can be shaped. > > Is this correct or is there a way of shaping incoming traffic? > > > > The problem could possibly be overcome if there is a way of routing > > traffic through a virtual host. Any tips on how to go about that? > > > > -- > > Manfred > > > > > > _______________________________________________ > > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ > > > > > > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/ >
