Fragmentation problem with Wlan Controler 4402 due to LWAPP header overhead

Unanswered Question
Jun 25th, 2008

Hello there,

I have following situation.

network---wlan controller4402----FW1---MPLS---FW2---Access points----networks

I can see very big amount of fragmented packets coming to FW2 and getting dropped in one moment. After those packets get dropped, access points get disconnected

I wonder, is there any documentation, or maybe some of you guys can give me some tip/trick how to set up WLC4402 to use TCP MSS, PMTU or any other settings that can help that IP Datagrams between 4402 and access points don't go over 1300B

Thanks a lot for any help



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
miloskv Wed, 06/25/2008 - 13:59


Thanks for your response.

I'm a bit confused watching this document you gave me. I don't know which part of it can be related to prevention of IP Fragments between controller and AP-s.

Problem is that controller is located on one side of the network, and we have FW (non cisco), MPLS network, other FW and then APs

other FW across MPLS receive a lot of fragments, which of course should be defragmented for session inspection, so this leads to large CPU utilization and fragment drops.

If we can instruct controller to set MSS bits or to be involved in PMTU, then we could try to prevent end hosts to ever create large TCP/UDP segments/datagrams to be sent via LWAPP tunnel

Thanks for any advice



Scott Fella Wed, 06/25/2008 - 14:08

Well the problem is that it was designed for AP to WLC locally and not really accross a WAN, unless you implement H-REAP. There is no configuration to set on the WLC nor the AP to change this at all Since the WLC knows how to put the fragmented packet back together.


This Discussion