How to do a proper Queue Tree on a AP?
What about the “Default Forward” option, do we leave it or remove it?
P.S. It seems that for proper QoS at the AP interface, we need to set “default-forwarding=no”. Anyone can help with any pointers?
Do you currently have WMM enabled on the accesspoints?
Or is your intention to setup QoS on your backhaul wireless links?
I do not have WMM enabled as I do not know how it works and I don’t believe it will help me. But if it can help on the AP - how?
The real questions are:
For ethernet interfaces I usually manage upload and download with
separate queue trees and separate packet markings.
But for the AP wlan1 interface, maybe I should mark all packets
traveling in all directions and manage them together with one Queue
Tree?
My friend, default-forwarding=no will disable the AP acting like a
switch? If this option is disabled, I need the client on the AP
to communicate THROUGH the router - through the prerouting forwarding
and postrouting chains, so that I can drop most of their unneeded
traffic and actually achieve REAL PACKET QUEUE CONTROL via MANGLING
ALL packets that travel through the AP in any direction and managing
them with Queue Tree.
But I need some pointers on this… 
Thanks.
I need to achieve QoS at the AP interface. I need pointers on this.
Maybe this is the correct approach? :: If default-forwarding=yes there
will be some packets that will be forwarded on Ethernet layer, which
excludes them from the possibility of being involved in a Queue Tree.
So I will set default-forwarding=no. Wireless interfaces work with
faster rate in what I can express with “half duplex mode” than in “full duplex mode”. So I will
make a Queue Tree that manages download and upload packets together
and has one max-limit for all of them, which will hopefully coresspond to the lower layer capabilities of an AP Wi-Fi interface.
Is this correct? Or can you suggest something better?
I found this:
hot to forbid Windows file sharing in wireless ???
Is this correct? Do I really need to set all the clients’ subnet masks to /32 ?!
I would be good if someone could share their thoughts about QoS on the AP.
I think you might be in the wrong section of the forum.
So disabling default-forward is a must. It should be so by default, consider it a feature change request. Also broadcasts should be filtered…
Yes, to apply a correct QoS on a “wireless” access point that uses 802.11 you may NOT want those stations forwarding packets each other without QoS or even not doing traffic shape. However, each station must be on a different network to do this (routed traffic). By deploying bigger networks than /30, stations that want to talk to each other on the same access point without forwarding “over the air” simply will not work, obviously.
Ozelo
WMM- works by dividing traffic into 4 access categories: background, best effort, video, voice. QoS policy (different handling of access categories) is applied on transmitted packets, therefore it is transmitting device is treating different packets differently - that is - e.g. AP does not have control over how clients are transmitting packets, and clients do not have control over how AP transmits packets.
“Default Forward” is a option to open port to your local network.Client see another client. You can set up this option in access list or turn OFF on wireless interface.
Shape your traffic you can do very simply.
1.Mark all packets “ALL”(or mark as your like-http,p2p,…) IP/Firewall/Mangle.
2.Make PCQ Queue by destination and source address
3.Make Queues Tree-parent with public and local interface and…
4.Done
the best QoS is good signal(-65) and CCQ(over 60%) between AP and client:-)
I have a lot of problems with the voip traffic in my network.
to IP level I have a lot of queue and traffic controll, but the delays are introduced to level wireless in PmP
it’s better to use the WMM or Nstreme-polling in order to improve voip quality?
Wmm is compatible with compression?
thanks mikrotik forum
In case one needs to setup the packet queue on the AP interface, one needs to think how to do it considering it is a wireless interface that behaves very differently than a wired eth interface. Therefore I started this thread.
I’ve recently been implementing the DSCP based QoS as listed here: http://wiki.mikrotik.com/wiki/DSCP_based_QoS_with_HTB
Works well by tagging outbound traffic and setting the expected speed for the external internet connection.