Thanx for the wishes :D Yes i'm used to compile kernels (but don't patching)... I did not try yet to use the new script since in fact i don't believe i have IMQ neither ESFQ and my box is doing it's work ok with more than 400 users... don't wan to mess with it. It's congested but it's working. The good news is that my box is acting as a routing and i could use my lan (eth0) conn to control the incoming traffic from the internet (eth1) without the help of IMQ. So my requirments would be to slow down outgoing http, ftp and smtp. Also would need to prioritize VPN clients. Affortunately all my VPN clients have fixed IP addresses so i can mark the packets after the PPTP de-encapsulation (going out through eth0). Now it looks easier than before... (until i do the update). My idea is to use HTBF with some leafs: 1.- http && ftp (bulky non priority traffic) 2.- smtp (bulky but high prio) 3.- vpn/pptp (bulky and high prio) I would like to keep the response time low for ssh because of the admin tasks are majorly achieved through it. Is it best to use tc filters or iptables packet marking ? For me it's easier iptables... Any further suggestion ? Guillermo On Thu, 2004-06-24 at 16:40, Ed Wildgoose wrote: > >Give me sometime to understand what u said ! > >I went into the Howto and started reading all over. > >Discovered what imq devices are, and remembered what ESFQ was. > >Also went to the http://digriz.org.uk/jdg-qos-script/ ans started > >studying it. > > > > > > You just have to plough through the Howto. Basically though these > things classify the *outgoing* data into a couple of queues, then they > release the packets at a programmable maximum rate. You can either do > the filtering in "tc", or just do it in iptables (more flexible). > > The key thing is that its outgoing stuff only, so you either do it on a > machine that is routing (cos then the other interface will effectively > be your "out" one). Or you use IMQ on the incoming interface, which > simulates having something just in front of the normal interface (hence > you can attach outgoing filters to it). > > The various qdiscs differ in implementation and number of params, but > that is the basic idea. HTB is the simplest because you just create a > couple of queues and set rates on them - everything else is done in > iptables. > > >My kernel is 2.4.18-14 (RH8) and planing to upgrade to FC1 (not yet > >confident with FC2). > > > >How can i know if both IMQ and ESFQ is available in my actual kernel? > > > > > > Hmm, well the script will error if you haven't. Redhat has a lot of > stuff compiled in, but if not then you are going to have a lot of > compiling ahead. You need a new kernel, new tc, and each will need > patches because neither of these things is mainstream yet.... It's not > hard if you have done this before (takes 20 mins), but if you haven't > then it's going to need you to set an afternoon aside to learn how to do > it (there are dozens of sites on how to compile the kernel) > > Good luck > > Ed W -- Guillermo Gomez <ggomez@xxxxxxxxxxxxx> neotech _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
