Hello, Can anybody point me to the information about how protocols are classified into what ampdu types? I am also interested in how the packets are detected and or classified and if that is done automatically or if it’s up to us to mark them?
Basically I’m tuning links for best performance with real life traffic but I can’t seem to find out if traffic is classified as an ampd priority type somehow automatically or if we have to do it manually? The Manuel is a bit bare on info on these matters? It doesn’t even say what type is what!
Use your mangle to set priority, that corresponds to the “ampdu”. Don’t check for latency sensitive applications, as it is possible it would create latency.
Well if anybody is interested I found some info in ubiquity forums and some cisco site about this and I would hope it’s the same with MT.
The packets are not marked automatically so it’s up to us to mark them at source. Most VOIP units do it by default. But once done they should follow as below:
ampdu transmit priority [0-7]
Assigns a class of service transmit priority to the selected 802.11n radio interface as follows:
•Best Effort (0)
•Background (1)
•Spare (2)
•Excellent (3)
•Control Lead (4)
•Video <100ms Latency (5)
•Voice <100ms Latency (6)
•Network Control (7)
I must say I am surprised how this info is not in the manual and was quite difficult to find!!
Just to clarify - ht-ampdu-priorities setting only specifies frame priorities for which AMPDU usage will get negotiated, it does not itself enable any assigning of priorities (classifying) and does not make interface act in different way on packets with different priorities, just as explained in: http://wiki.mikrotik.com/wiki/Manual:Interface/Wireless
Wireless interface will only act on packet priority if WMM is enabled and it is explained here: http://wiki.mikrotik.com/wiki/Manual:WMM
Albeit the information is scattered among different places, it is a bit unfair to say that there is no documentation .
[/quote]Albeit the information is scattered among different places, it is a bit unfair to say that there is no documentation .[/quote]
Well I think it was really the specific details about how the system works under the hood. Which you kind of need to know to use it properly! But I guess that is more like standard 802.11 info rather than Mikrotik info. But I still needed to know it and was quite hard to find.
I understand spire2z that he says that everything is unclear.
The illiterations and explanations could be better documented.
This is not a reproach but a well-elaborated explanation documented where necessary with an example would create more clarity.
As everything stands together then can you understand well.
If you speak of priorities, you can document that you do that via mangle rules.
And show how you have to do that.
This requires more work but creates a lot more clarity.
.