It is possible to set up the API parameters when editing router details:
API turning on - activates the API connection. To do so, click API in IP -> Services
DNS - DNS server settings
NAT - activates the NAT. Very important parameter which creates a rule in IP Firewall NAT. As the rules for Mangle and Queue tree have been created in different places when the NAT is not active, the packet marking is being processed in prerouting chain and the queues in global-in.

When the NAT is active, the packet marking moves to forward and the queues are being created in global-out
QoS - QoS turning on
Connection marks - marks particular connections as well as all the packets in connections
Shaping - turns on bandwidth management and its settings
Shaping type - type of shaping
Queue type - queue creating algorithm

EN-API-1.png

Let's check out shaping options offered by MikroTik and incorporated into MikroBill:

1. No one - there will be no rules created for user's bandwidth limitation

2. Queue tree - an extensive system creating particular records in the Queue tree both for download and upload, based upon the packet marking from/to a particular customer's IP address. This type of shaping allows user aggregation regarding the tariff groups. Big advantage of this type of shaping is the clarity of Queue Tree structure. However, high volume of created rules make it slightly difficult to manage which makes this type more suitable for less or mid-occupied routers. To operate 1 central shaper for 500 customers or more, it is necessary to use another algorithm - PCQ with address list. An example of simple Queue Tree created by MikroBIll can be seen on the following figure:

A-API-2.png

3. Simple queue - the most simple shaping where the rules are being created in Queues -> Simple Queue and the customers have been limited by the IP address in the same way that the Queue Tree does. There are only disadvantages of Simple Queue, the impossibility of aggregation and big rush for the router even when there is a moderate number of customers. See the following figure:

A-API-3.png

4. Simple queue with aggregation - to use the Simple Queue together with customer aggregation, use the Simple Queue Tree. MikroBill creates rules for Simple but these depend on the main rules over the parent/child nodes. See the following figure showing the Simple queue with aggregation:

A-API-4.png

5. PCQ with Address List - this type of shaping places the IP addresses of customers into the address list regarding their tariffs and there are rules being created in the Queue Tree (only for tariffs, not for sustomers). The speeds are being reduced over the PCQ settings in Queue Type. See the following figure showing where the shaping rules are being entered (MikroBill inputs them into the router over the API regarding PCQ shaping with Address List):

A-API-5.png

© 2013 MikroBill, all rights reserved