IMQ has de advantage that you can filter packets you need to control the traffic using iptables and the packets pass the contrack layer too (if you use "state" module). For example, you need to classify traffic from/to clients and by type too, you can do it with a single interface with tc and complex filters/classes/qdiscs, but with IMQ, you can use the traffic classification into the interface and the clients traffic into an IMQ interface.. Another example, you have many interfaces that comunicates with many lan's and you want to use the same classification for all them, then use only one IMQ interface and the outgoing/incoming to/from that interfaces redirect to it using IMQ target. That are two examples, many users have more real applications of IMQ, perhaps they want to say us. Regards El Jue, 8 de Marzo de 2007, 11:29, Simone84bo escribió: > Hi all, > I manage somo interface in output. > I know that i can send packet to the single interface using routing > tables. > I use IMQ to shape ingress traffic but why i would have to use IMQ on > postrouting? > When IMQ, on egress, give me advantages? and what are this advantages? > > Thanks > Bye > Simone > -- > Email.it, the professional e-mail, gratis per te: http://www.email.it/f > > Sponsor: > > Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=6119&d=20070308 > > > _______________________________________________ > LARTC mailing list > LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
