Adding proper queues

Having the main queues (parent), the subscribers are assigned to 'parent' and at appropriately priorities they would divide theirs band. The scripts, which are selected well, will make the situation effectively and quickly for entire range: from 2 to 254.

(script)
:for z from 2 to 254 do={ /queue tree add parent=Download packet-mark=( $z . download ) limit- at=32000 queue=sfq priority=7 max-limit=256000 }

The script will generate 254 queues. Each of those will be limiting the download for single mark (IP address), guaranteeing it the 32Kbps bandwidth and limiting to 256Kbps. The guarantee would be consisted in accounting two virtually queues: first, the limit-at counting (guaranteed speed), and the second one, max-limit (maximal speed), taking into consideration that limit-at queue will proceed through separate and higher prioritised path for the moment of limit-at value exceeding.
After limit-at exceeding, the value of priority becomes ignorable (an equal as lowest: 8). It means, that users who blocking up the link would be ignored at the moment, when new user will have wanted to use to 32Kbps of bandwidth. Thanks to such action- one might receive a quite steady put of link and also appropriate access level for service. The limit-at value should be equal to divided real value of link by users number and multiplied by simultaneity ratio (at about 3).

(script)
:for b from 2 to 254 do={ /queue tree add parent=Upload packet-mark=( $b . upload ) limit-at=32000 queue=sfq priority=7 max-limit=220000 }

Now, the Upload. I recommend saving of upload, even for symmetrical links, especially by large overbooking (when we send more than we have), because lower of upload in p2p programs causes low of download load.

After finishing ours queues should look like follow example:

.:see picture:.

(this example comes from working router, which was analogous configured with a little differents only).