Hi all!
I'm currently working on the QoS part of my study.
For the HREAP (FlexConnect AP) locally switched, connected on a trunk port,
it is recommended to trust CoS on the switch. I completely understand this
point, to preserve the priority cos tag.
However, I was wondering how could the cos tag be preserved for the CAPWAP
control traffic? Indeed, HREAP APs communicate with the controller over the
native vlan. By default this vlan is not tagged with a 802.1q header, so no
cos value can be added?
I captured traffic on a HREAP AP link, and I can see the following:
- 802.11 management frames are CAPWAP-encapsulated and sent to the
controller with no 802.1q tag (so no cos priority)
- CAPWAP control frames (Discovery/DTLS) are tagged with 802.1q vlan
(native vlan), and the cos is present (cos = 6)
I can see also some frames with the 802.1q header of the native vlan with a
cos = 4. These frames are identified by Wireshark:
- as 802.11 frames, encapsulated with CAPWAP (from WLC to AP)
- the 802.11 part is identified as the WLCCP protocol
- the 802.11 frame encapsulated has the following addresses:
- Receiver + Dest. address: STA (laptop)
- Transmitter + Source address: LAP
I don't know what are these specific frames. If someone has the answer, I'm
interested
Andre
_______________________________________________
Free CCIE R&S, Collaboration, Data Center, Wireless & Security Videos ::
iPexpert on YouTube: www.youtube.com/ipexpertinc
