Technical data

4. Packages
QOS_FILTER_1_OPTION=''
QOS_FILTER_2_CLASS='2'
QOS_FILTER_2_IP_INTERN='192.168.0.3'
QOS_FILTER_2_IP_EXTERN=''
QOS_FILTER_2_PORT=''
QOS_FILTER_2_PORT_TYPE=''
QOS_FILTER_2_OPTION=''
QOS_FILTER_3_CLASS='3'
QOS_FILTER_3_IP_INTERN='192.168.0.4'
QOS_FILTER_3_IP_EXTERN=''
QOS_FILTER_3_PORT=''
QOS_FILTER_3_PORT_TYPE=''
QOS_FILTER_3_OPTION=''
Option QOS_INTERNET_DEFAULT_UP is set to 0 because upstream should not be regulated.
Example 2
This example targets at spreading bandwidth between 2 client PCs and then those client
bandwidths between one port and the remaining traffic on the client.
We create 2 classes at first with the complete speed for each client and attach them directly
to the interface for “up” res. “down” (see example 1). No we create two additional classes for
the first client attached to the first class. These classes are created in the same way like the
first ones directly attached to the interface except for one difference: QOS_CLASS_x_PARENT is not
0 but the number of the parent class it is attached to. If this for example is QOS_CLASS_1 the
classes’ QOS_CLASS_1 has to be set to 1. The same is applied for the second client PC. Attach
two subclasses to the class for the second PC. This could be done for an infinite number of
PCs if needed. Subclasses of a class can also be created in the amount needed.
This is our skeleton. Now filters have to be defined to assign traffic to the classes (see
example 1).
2 filters have to be created for each client. One filter on a port and one for the remaining
traffic of the client. Filter sequence is of essential importance here. First filter the port and
then the rest. The other way round the filter for the remaining traffic would assign all traffic
to its class (including the port traffic).
Let’s call the interface 0, the 6 classes 1, 2, 3, 4, 5, and 6 and the 4 filters F1, F2, F3 and
F4. The scenario looks like this image 4.7.
o
1
3
2
4
5
6
F1 F2 F3 F4
Figure 4.8.: Example 2
214