What’s the different between Simple que and Queue tree
Some day I was asked a question as it
Check the config and manual
found the Simple queue can make the same funtion as Queue tree
So …Any one can tell me the different of them
‘Queue simple’ and ‘queue tree’ provide few different matchers, that’s why configuration for ‘queue tree’ and ‘queue simple’ is not the same. Almost all configuration is possible either with ‘queue simple’ or ‘queue tree’ (without using two of them). Indeed documentation provides very detailed explanation about them, and Winbox provides visual description about available matchers.
Could you be more specific about the question (what kind of difference you want to know ) ?
Thank you for you advice, Sergejs.
What I meaning is
When I want to limit customer download speed in my network
Which type queue is the better way to make it?
Simple que or Quer tree
Simple que let us make it by IP
It also can work with PCQ and marking packet priority.
Queue Tree not limit by IP
But it same working with marking packet adn priority
So I puzzle whether I should chooes when I want to limit the customer download speed in LAN
Simple Queue marks packets, and make invisible leaf in Queue Tree.
Simple queue can limit upload/download to an IP
Queue tree uses Mangle packet marks to do the limitations, Mangle can match any traffic. For example you can use it to match only P2P traffic coming from specific customers at a specific time. And then use the mark to make a Queue Tree.
There is a lot of things different in these two Queue options.
Normis
You gave me a good support
Let me member the small different between them.
I love MT better
K.
I have one question regarding the subject.
Can you have simple queues for limiting MAX bandwidth per client, and, at the same time, queue tree for having priority by traffic ?
I mean, from 512k for three clients, have them to go ymess, skype and voip prioriti +1 regarding “bulk” http traffic ?
Is it possible ?
If there is an example somewhere, please show me the road…
no easy solution on this one 
…
key is in the order or the queue’s ..
— next add …
example …
on our network we use 192.168.0.0/16 for internal use
192.168.79.0/24 is the range for PPPoE user’s on that AP
first i setup that users have 1mbps/1mbps (i round it to 1.100.000 bits per second )when comunicate on same AP we do that with
/queue simple add dst-address=192.168.79.0/24 target-addresses=192.168.79.0/32 max-limit=1100000/1100000
/queue simple add dst-address=192.168.79.1/24 target-addresses=192.168.79.0/32 max-limit=1100000/1100000
/queue simple add dst-address=192.168.79.2/24 target-addresses=192.168.79.0/32 max-limit=1100000/1100000
… and so on up to .255
/queue simple add dst-address=192.168.79.0/24 target-addresses=192.168.79.255/32 max-limit=1100000/1100000
next we define that we want user to have 512k (530.000) when communicate with rest of internal network
/queue simple add dst-address=192.168.79.0/24 target-addresses=192.168.79.0/32 max-limit=530000/530000
/queue simple add dst-address=192.168.79.0/24 target-addresses=192.168.79.1/32 max-limit=530000/530000
…
/queue simple add dst-address=192.168.79.0/24 target-addresses=192.168.79.255/32 max-limit=530000/530000
that shape traffic so that you have internal trafic (DC++ and tons of ‘‘educational’’ movies and ‘free’’ software … few 400gb disk ) … so user will use internal network more then outside
next you have to define a rules how much bandwidth do you have and willing to give to users if you have 512k/256k .. maybe .. just maybe you serv your user’s with 64k/16k … allways reserve upload that you may be need it for some cheap sattelite downloading system and some proxy .. .. proxy can help you a lot on small internet connection
/queue simple add dst-address=0.0.0.0/0 target-addresses=192.168.79.0/32 max-limit=64000/16000
etc..
if need more help give me your msn …
The last post is very powerfully educating. A verified bigger tutorial of this sort Must be put on the wiki! Thank you.