I created two simple queues with target destination being a linux ftp server out on our network.
The first queue numbered 1, was left totally vanilla, meaning no changes were made to its default settings, in particular up and download speeds are set to unlimited.
The second queue numbered 2 is identical to the first queue, except up and download speeds are set to 3 megs and 5 megs.
When I run an ftp session from my desktop to the remote ftp server, I get 3x5 and the counters go up on the second queue but not on the first.
I believe queues should be handled in the order they are presented, so why is the first queue being ignored?
Thank you I watched the whole thing, very interesting, however it did not approach our immediate problem.
We are not using fasttrack nor masquerade.
We have two linux routers on our internal network that have a single tik in between them that has the queue with a target address of the most remote linux box.
If we place a single simple queue with max set to unlimited (max=0/0) the queue is ignored.
If we set a finite max (max=3/5) the queue is used.
If we set a true max like max=100/100, the queue is also used.
Simple queues are processed sequentially, once a packet matches one, it won’t proceed to the next same-level simple queue.
That’s the reason why
Setting max-limit=0/0 does mean no limitation. If you check wiki example it’s used as first rule so that traffic from the server is matched first and so, prevented from being processed on any further simple queues that may match.
I’m not sure what do you want to achieve. Do you want to set a “global” limit for FTP access to say 100Mbps, then limit each user to 3/5Mbps?
Due to queues implementation if you make a simple queue and only specify target, then this queue does nothing with packets passing through it. If you would change queue type to any other than default one or specify some max-limit only then it will be registered into Kernel and will start to work.