On Mon, May 20, 2002 at 09:24:43AM -0500, Charles Menzes wrote: > > > > You set up CBQ/HTB rules to define the queueing behavior for the > > outbound traffic. It means that certain packets would go to certain > > queues (scheduled to be sent out). > > Now that you have that you need to somehow identify which packets > > go to which queue. Here comes your criteria about ip/port or any other > > packet identifier. The role of netfilter in this is to identify > > these packets and mark them so the queueing subsystem can direct them > > to the right queue. However, tc (the program which helps you set up > > different queues and rules) has the ability to identify the packets > > itself so you do not need use netfilter perse to mark them. > > > > I'd suggest you to take a "good" look at http://lartc.org/ for > > information as to how to do it. A lot of information to digest... > > > > Ramin, > Thanks for your answer, and the pointer. I'm starting to digest > the website now. I've been using Zeigler's 2nd edition book on iptables > to make the transition from ipchains. Is there documentation outside > of the lartc website that someone may have published?
For the traffic control the information is scattered. http://lartc.org/ is the best place to start. One of my friends has worked hard during the time that there was virtually no info on tc & co and set up a web site to help us http://www.docum.org/. I'm pretty sure that there are other friendly people having done just that as well. But, netfilter has had much better documentation from day one. A good starting point is http://www.netfilter.org/ of course. For advanced routing http://www.policyrouting.org/ is an excellent site by Matthew G. Marsh who BTW has also a book: http://www.policyrouting.org/PolicyRoutingBook/TOC.html >From these three concepts the first one is what you need and enforced by Murphy, is the most difficult one ;-) Ramin > > Thanks -Charles >
