Netonix Forums

Hi Folks,

I know this has been asked many times can someone point me in the right direction or provide some sort of guidance for QoS on Netonix gear. The overall goal is to have a complete QoS Solution for the network in defending from bandwidth hogs but still allow critical traffic through in a prioritized manner like Streaming/Voice to start while providing customers the speeds they are paying for.

Mikrotik Routers - Edge/Core
Netonix Switches - Each tower


I've read the following links:

QoS/Rate Limit at port issue?
viewtopic.php?f=6&t=4934

QoS per port
viewtopic.php?f=6&t=3921

what about shaping?
https://forums.netonix.com/viewtopic.php?f=5&t=534Feature request: Set CoS (PCP) and DSCP
viewtopic.php?f=6&t=3328&start=0

Thanks in advance!

You won't have the desired result. The switch is not aware of how much bandwidith is left on your wirelesss radios, only on the ethernet ports up to the radios.

If you want to eliminate bandwidth hogs, you will need an external solution like preseem.

Okay, thanks for your answer! So, there is no basic guide on QoS in general on the switches?

No guide but the QoS table is self explain by the GUI if you understand how QoS and traffic shaping work.

First, the port configuration:
Scheduler strict = 7>6>1>0. As long as the're paquets in a higher priority queue, lower queues will be ignored so if the're 1Gb/s of data on queue 7, other queues traffic will never pass.

WRR (Weight Round Robin) = All queue have same weight and will pass number of paquets equally between each queue. Note that paquets don't have the same size so bandwidth by queue will not be the same, only the number of paquets.
https://en.wikipedia.org/wiki/Weighted_round_robin

Once interface configure, you can add rule at the top to indicate to which queue you want to send paquet. By exemple, if your VoIP is on vlan 200, your can add a rule to send it in a specific queue like 5.

port = all, type = VLAN ID, value = 200, queue =5.

Tips: If you want your netonix switch to handle QoS on your radios, set a TX et RX limit under (with a margin) of the radio capacity.

It is generally best to have your radios do the QoS since they are aware of how much bandwidth they have and can act accordingly.

mducharme wrote:It is generally best to have your radios do the QoS

It's really depend of the radio. Some have good QoS integration, other not.
Several vendor have poor QoS because the want the best throughput possible and for this, you need to overload the radio. It not just specific to wireless, you can see this also in carrier class wired equipments. You should read about bufferbloat, the problem is well explain (buffer too large and several parquets are keep while they should be drop. The result broke TCP bandwidth adjustment mechanism and create jitter bloat).
The same is done be several low end radio vendors, they try to get the best throughput by overloading the radio but with wireless, the result is way worst than on wired devices. It's well know that you should never overload a some popular low end vendor radios. In those case, it's better to use a software like preseem that will inspect the quality of transfer and adjust traffic shaping until the quality of the streams are fine.