According to this document, you need to open UDP 1024 - 65535 between WLC (source) and APs (dest).

And it's correct - I can see these sessions getting dropped on my firewall since I didn't open those ports.

I only opened CAPWAP 5246-5247 from AP to WLC, and it seems to be working just fine. I can see my APs on my WLC, and configuration changes work.

So my question is : what is the WLC trying to send to my APs with those new UDP sessions ? I cannot find any information anywhere, and cannot run a packet capture.

  • Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could post and accept your own answer. – Ron Maupin Dec 31 '20 at 3:54

It's right there in the footnote:

Arbitrary port number is assigned to every AP from range 1024 - 65535 when the AP joins the WLC. The WLC uses the number as the Destination Port for CAPWAP Ctl/Data as long as the AP is connected.

  • If I made this post, that's exactly because I did not understand the footnote. What is the session established by the AP used for then ? – pHeoz Nov 9 '20 at 15:18

The WLC uses the number as the Destination Port for CAPWAP Ctl/Data [...]

In this context "Ctl" (Control) is the management traffic between the A.P. itself and the controller (pushing configuration, gathering information, firmware updates, etc...), and "Data" is the data streams from the wireless clients connected to this A.P.

So when the A.P. contact the WLC at startup, a CAPWAP tunnel is establish between them, on a random UDP port.

All communication between the AP and the WLC as well as all traffic from the wireless clients to the other parts of the network are encapsulated in this capwap tunnel.

Note: you can configure the WLC so the client traffic is locally switched by the A.P. but this mode has some drawback. In this case, only the control traffic will use the CAPWAP tunnel.

  • That's my entire point : the AP creates a CAPWAP tunnel to the WLC. But once this has been established, the WLC attempts to communicate to the AP on a new, unrelated session ! That means traffic is getting dropped on the FW because I did not allow WLC (source) => AP (destination). I'm trying to understand why the WLC behaves like that. – pHeoz Nov 9 '20 at 18:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.