Although it is generally recommended that you use the traffic shaper wizards when getting started with traffic shaping, for this exercise we will avoid using them, since the rules the wizard will implement would require significant modification. We will begin by navigating to Firewall | Traffic Shaper and selecting the Limiters tab.

We require that developers and engineering receive 100 Mbps of downstream bandwidth, with 60 Mbps going to developers. We also will gives developers and engineering 25 Mbps of upstream bandwidth, with 15 Mbps going to developers. To do this, we will set up two limiters: a limiter for download bandwidth and one for upload bandwidth. Each of these limiters will have two children (one for developers and one for engineering). We proceed as follows:

1. Click on the New Limiter button.
2. Check the Enable checkbox.
3. In the Name edit box, type qDOWNLOAD.
4. For Bandwidth, enter 100 in the edit box and select Mbit/s in the drop-down box.
5. We can leave Mask unchanged. You can enter a brief description (for example, Download queue for developers/engineering).
6. Click on the Save button; then click on the Apply Changes button.
7. Click on the qDOWNLOAD queue on the left sidebar; then click on the Add new Queue button to create the first of the child queues.
8. Click on the Enable checkbox.
9. In the Name field, type qDLDEV.
10. Again, Mask can be left unchanged; you may enter a brief description (for example, Download queue for developers).
11. Under Advanced Options, in the Weight field, type 60 (so that developers gets a 60% share of 100 Mbps, or 60 Mbps).
12. Click on the Save button and then click on Apply Changes.
13. Click on the qDOWNLOAD queue on the left sidebar and click on the Add New Queue button. Create a new child queue named qDLENG by checking the Enable checkbox and specifying qDLENG in the Name field.
14. Under Advanced Options, in the Weight field, type 40 (so that engineering gets a 40% share of 100 Mbps, or 40 Mbps).

15. Click on the Save button; then click on Apply Changes.
16. Follow the same procedure to create a queue called qUPLOAD with a total bandwidth of 25 Mbps. Create two child queues called qULDEV with a 60% share of bandwidth, and qULENG with a 40% share of bandwidth.

We now have a set of queues for the developers and engineering networks, but they are of no use until we create rules to send traffic to them. Navigate to Firewall | Rules and click on the Floating tab. We need to create four rules: an upload and download queue for each interface:

1. Click on one of the Add buttons at the bottom of the page.
2. In the Action drop-down box, select Match.
3. In the Interface listbox, select developers.
4. In the Direction drop-down box, select out.
5. All traffic to and from the interface is going to the queue, so in the Protocol drop-down box, select any.
6. You may enter a brief description in the Description edit box (for example, developers download queue rule).
7. Click on the Show Advanced button.
8. In Advanced Options, scroll down to the In/Out pipe drop-down boxes and select qDLDEV as the In pipe.
9. Click on the Save button at the bottom of the page; when the main Floating rule page reloads, click on the Apply Changes button.
10. Create a rule for the developers upload queue by clicking on the Copy icon for the previously created rule, changing the Direction to in and changing the In pipe to qULDEV. (You may also enter a brief description in the Description field.). Click on the Save button when done and then click on the Apply Changes button on the main Floating rules page.
11. Create rules for the engineering download and upload queues. Both queues should have engineering set as the Interface and any selected in the Protocol drop-down box. The download queue should have the Direction set to out and the In pipe set to qDLENG. The upload queue should have the Direction set to in and the In pipe set to qULENG.

We now have queues for both developers and engineering that meet our traffic shaping requirements for both networks.