Packet Loss and Extremely slow APs

[RTPB]

Hello, Our setup has a fortigate 100D managing 3 fortiAPs. All 3 of the APs experience around 5% packet loss and average around 180ms response time when executing pings. Everything on the LAN is fine, I can ping out from the 100D and never drop a packet, same with every PC on the LAN. Only devices connecting to the Wifi are having issues. We have separated each AP to broadcast on it own channel. Originally we had traffic shaping enabled limiting the bandwidth and set the public SSID to low priority. However it' s currently disabled, but it made no difference either way. Currently stumped on what else to try. Any ideas?

[Bromont_FTNT]

How many other APs are in the area? If you connect to the 5GHz band do you still see the issues?

[RTPB]

We have 3 APs and I tried the 5ghz band yesterday. The 5ghz didn' t increase speed and a few devices can' t even connect to it so if it had been better it wouldn' t have been an option. Any other ideas? Possibly some sort of interference?

[Bromont_FTNT]

Trying the 5GHz band is just a troubleshooting step as there is typically less congestion there. What model AP do you have, what firmware are they and the Fortigate on? Packet loss was still an issue on 5GHz What speeds are you seeing?

[RTPB]

The APs are 221B. Initially we just used the firwmare that came on the AP (not sure which version) since then we have upgraded all the firmware to the latest versions for the APs and the Fortigate itself. Download speeds can vary using speedtest. I range anywhere from 3-8MB/s download. below is a sample ping when connected to an AP. You can see the time gradually building, then time out. 64 bytes from 74.125.228.103: icmp_seq=0 ttl=53 time=160.356 ms 64 bytes from 74.125.228.103: icmp_seq=1 ttl=53 time=38.637 ms 64 bytes from 74.125.228.103: icmp_seq=2 ttl=53 time=52.598 ms 64 bytes from 74.125.228.103: icmp_seq=3 ttl=53 time=134.955 ms 64 bytes from 74.125.228.103: icmp_seq=4 ttl=53 time=458.302 ms 64 bytes from 74.125.228.103: icmp_seq=5 ttl=53 time=495.629 ms 64 bytes from 74.125.228.103: icmp_seq=6 ttl=53 time=789.920 ms 64 bytes from 74.125.228.103: icmp_seq=7 ttl=53 time=1011.586 ms 64 bytes from 74.125.228.103: icmp_seq=10 ttl=53 time=1860.627 ms 64 bytes from 74.125.228.103: icmp_seq=13 ttl=53 time=2132.839 ms Request timeout for icmp_seq 8 64 bytes from 74.125.228.103: icmp_seq=14 ttl=53 time=2082.308 ms Request timeout for icmp_seq 9 64 bytes from 74.125.228.103: icmp_seq=16 ttl=53 time=2006.642 ms Request timeout for icmp_seq 11 64 bytes from 74.125.228.103: icmp_seq=17 ttl=53 time=2078.974 ms Request timeout for icmp_seq 12 64 bytes from 74.125.228.103: icmp_seq=18 ttl=53 time=2024.516 ms 64 bytes from 74.125.228.103: icmp_seq=19 ttl=53 time=1861.078 ms 64 bytes from 74.125.228.103: icmp_seq=20 ttl=53 time=1507.904 ms 64 bytes from 74.125.228.103: icmp_seq=21 ttl=53 time=1278.739 ms 64 bytes from 74.125.228.103: icmp_seq=22 ttl=53 time=801.436 ms 64 bytes from 74.125.228.103: icmp_seq=23 ttl=53 time=319.324 ms 64 bytes from 74.125.228.103: icmp_seq=24 ttl=53 time=50.802 ms Request timeout for icmp_seq 15 64 bytes from 74.125.228.103: icmp_seq=25 ttl=53 time=41.962 ms 64 bytes from 74.125.228.103: icmp_seq=26 ttl=53 time=48.199 ms 64 bytes from 74.125.228.103: icmp_seq=27 ttl=53 time=37.394 ms 64 bytes from 74.125.228.103: icmp_seq=28 ttl=53 time=54.919 ms 64 bytes from 74.125.228.103: icmp_seq=29 ttl=53 time=46.529 ms 64 bytes from 74.125.228.103: icmp_seq=30 ttl=53 time=37.952 ms 64 bytes from 74.125.228.103: icmp_seq=31 ttl=53 time=34.731 ms 64 bytes from 74.125.228.103: icmp_seq=32 ttl=53 time=36.022 ms 64 bytes from 74.125.228.103: icmp_seq=33 ttl=53 time=34.727 ms 64 bytes from 74.125.228.103: icmp_seq=34 ttl=53 time=37.095 ms 64 bytes from 74.125.228.103: icmp_seq=35 ttl=53 time=39.811 ms 64 bytes from 74.125.228.103: icmp_seq=36 ttl=53 time=35.453 ms 64 bytes from 74.125.228.103: icmp_seq=37 ttl=53 time=36.310 ms 64 bytes from 74.125.228.103: icmp_seq=38 ttl=53 time=153.841 ms 64 bytes from 74.125.228.103: icmp_seq=39 ttl=53 time=133.698 ms

[kt000791]

Download/install ' inssider' to look at your nearby radio waves to see how many active AP' s are nearby and on what freq. Try different radios in the client. What is the signal strength at the client?

[markwen]

Just a thought. Have you checked to ensure your controller settings are configured for the correct region? (CLI) I had a similar issue, as the default is North America, and I' m in Australia. Once the correct region was set, the packetloss/throughput issue was resolved.

[Glinski]

Region is just what channels/Frequency you are allowed to use. Or is there something else I don' t know about the FortiAP? For example in North America you are allowed to use channel 1-11 and most of the world 1-13 (Japan get to use channel 14 on 11b). I would suggest like th previous poster to download inSSIDer and look at which channels/frequencies are being used and make sure his network don' t overlap, or at least overlap the least congested channel.

[Bromont_FTNT]

As RTPB stated, the speed does not improve when trying 5GHz so something else must be at play.

[Glinski]

What firmware is installed on the firewall itself?