In version 2.6 or something old like that we used to have simple queues for each host in our network that means every customer we have. and then do queuing with Queue Tree.
The only reason we used Simple queue for each host was to have graphing via MRTG on an external server and to be able to limit the speed on specific customers.
Now we use version 3.15 and we have our Queue Tree with the mangles in the firewall and marking packages. But the problem is that when we do that the simple queue’s doesn’t work, we can put our customers in there but can’t see the counters going.
I there any good explanation for that?
I planing to solve the graphing with Accounting and a script but that is not accurate.
I can say that we use static ip’s for all customers.
Any other idea how I should do to graph for each customer (host), or how i should do to get simple queues and tree queues to work at the same time
Did have this problem before.
One of the v3 versions they change Queue Type to
default-small as standard i think, try to change to default.
that did work for me.
Hope its work
hmms I have done some testing with Queue Tree and Simple Queues.
I tested with one Simple Queue With a target to an IP which I can test against.
Then I did some Queues in Queue Tree. one Main In and one Main Out with two children which I called as class 1 and class 2.
Without any mangles I could see Simple Queues counting.
But when started to mangle traffic I could see that the protocol or Port I mangled disappeared from Simple Queue’s counting and ended up in Queue Tree and counted there instead.
And as you said before, using Queue Type Default worked in Simple Queue but not when I was working with Queue Tree and mangles at the same time.
I can remember that this worked well in version 2.6. This test was run in Version 3.17
Conclusion: Queue Tree with Mangles and Simple Queue does not work along with each other, when I want to monitor one hosts traffic. I have no clue if this should work or not.