The policies are configured in the BQN and the RADIUS provides the name of the policy to apply. The policy name can be specified in AVP Mikrotik-Address-List.

To make the BQN take this AVP, disable the AVPs of higher priority:

As with dynamic policies, the policy name in BQN cannot have spaces, so spaces in the AVP are replaced in the BQN with underscores(“_”). For example, RADIUS policy “GOLD PLAN” will be “GOLD_PLAN” in the BQN and this is the name that should be used when configuring the static policy.

Initially, the policies are not configured. In Status->REST/Radius Policies, are listed the names of the policies coming from RADIUS, and from there they can be configured. For example, the next table shows three policies not yet configured (this is indicated by the SOURCE field as undefined), each of them with three provisioned subscribers and, so far, no subscriber active (with traffic):

For each of these policies coming from RADIUS, a Subscriber Rate Policy with the same name must be configured The GUI helps in the process:

1. In Status->Radius/REST->Policies, select the name of the policy. It will go to a form to define the policy parameters, with the right policy name already filled in.
2. In the form, specify speed limits in each direction and check those limits are according to the intent of the policy.

The process is repeated for each policy pending configuration. In this example, we have created three policies with downlink/uplink limits of de 20Mbps/10Mbps, 40Mbps/20Mbps and 60Mbps/30Mbps:

‍

Once the policies have been configured, they will appear with SOURCE config in Status->Radius/REST->Policies. In the following example, messages have been received related to three policies, with three subscribers each (SUBS-PROVISIONED):

‍

‍