Devices routinely experience high latency or loss of connection
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I've had 2 x EAP245 running for close to a year now, and they've largely been working well. There seem to be some parts of the house with signal issues (likely due to concrete walls with steel), but on the whole, great. The APs are plugged into a PoE switch, along with 4 other PoE devices (cameras). No issues with stability there.
For the past week or so, I've been experiencing the following on wireless clients (iPhones):
- High latency when viewing websites
- Although connected to wifi, no internet activity loads
To monitor this, I used ping on a laptop (connected via Ethernet).
- Pinging the router: < 1 ms, very little fluctuation
- Pinging the AP my phone is connected to: < 1 ms, very little fluctuation
- Pinging my phone (while very close to the AP, -45 dBm):
64 bytes from 192.168.100.27: icmp_seq=3384 ttl=64 time=105.526 ms 64 bytes from 192.168.100.27: icmp_seq=3385 ttl=64 time=4.183 ms 64 bytes from 192.168.100.27: icmp_seq=3386 ttl=64 time=41.757 ms 64 bytes from 192.168.100.27: icmp_seq=3387 ttl=64 time=2.169 ms 64 bytes from 192.168.100.27: icmp_seq=3388 ttl=64 time=7.743 ms 64 bytes from 192.168.100.27: icmp_seq=3389 ttl=64 time=109.487 ms 64 bytes from 192.168.100.27: icmp_seq=3390 ttl=64 time=27.620 ms 64 bytes from 192.168.100.27: icmp_seq=3391 ttl=64 time=45.689 ms 64 bytes from 192.168.100.27: icmp_seq=3392 ttl=64 time=3.790 ms 64 bytes from 192.168.100.27: icmp_seq=3393 ttl=64 time=8.903 ms 64 bytes from 192.168.100.27: icmp_seq=3394 ttl=64 time=7.709 ms 64 bytes from 192.168.100.27: icmp_seq=3395 ttl=64 time=2.199 ms 64 bytes from 192.168.100.27: icmp_seq=3396 ttl=64 time=3.042 ms 64 bytes from 192.168.100.27: icmp_seq=3397 ttl=64 time=13.931 ms Request timeout for icmp_seq 3418 Request timeout for icmp_seq 3419 Request timeout for icmp_seq 3420 Request timeout for icmp_seq 3421 Request timeout for icmp_seq 3422 Request timeout for icmp_seq 3423 Request timeout for icmp_seq 3424 Request timeout for icmp_seq 3425 Request timeout for icmp_seq 3426 Request timeout for icmp_seq 3427 Request timeout for icmp_seq 3428 Request timeout for icmp_seq 3429 Request timeout for icmp_seq 3430 Request timeout for icmp_seq 3431 Request timeout for icmp_seq 3432 64 bytes from 192.168.100.27: icmp_seq=3425 ttl=64 time=8048.897 ms 64 bytes from 192.168.100.27: icmp_seq=3426 ttl=64 time=7053.987 ms 64 bytes from 192.168.100.27: icmp_seq=3427 ttl=64 time=6063.000 ms Request timeout for icmp_seq 3436 Request timeout for icmp_seq 3437 Request timeout for icmp_seq 3438 Request timeout for icmp_seq 3439 64 bytes from 192.168.100.27: icmp_seq=3434 ttl=64 time=6871.918 ms 64 bytes from 192.168.100.27: icmp_seq=3435 ttl=64 time=5873.085 ms 64 bytes from 192.168.100.27: icmp_seq=3436 ttl=64 time=4872.611 ms 64 bytes from 192.168.100.27: icmp_seq=3437 ttl=64 time=3869.003 ms 64 bytes from 192.168.100.27: icmp_seq=3438 ttl=64 time=2993.016 ms 64 bytes from 192.168.100.27: icmp_seq=3441 ttl=64 time=6.076 ms 64 bytes from 192.168.100.27: icmp_seq=3442 ttl=64 time=4.204 ms 64 bytes from 192.168.100.27: icmp_seq=3443 ttl=64 time=9.332 ms 64 bytes from 192.168.100.27: icmp_seq=3444 ttl=64 time=8.039 ms 64 bytes from 192.168.100.27: icmp_seq=3445 ttl=64 time=222.486 ms 64 bytes from 192.168.100.27: icmp_seq=3446 ttl=64 time=76.731 ms 64 bytes from 192.168.100.27: icmp_seq=3447 ttl=64 time=2.381 ms 64 bytes from 192.168.100.27: icmp_seq=3448 ttl=64 time=9.920 ms 64 bytes from 192.168.100.27: icmp_seq=3449 ttl=64 time=2.270 ms 64 bytes from 192.168.100.27: icmp_seq=3450 ttl=64 time=2.549 ms 64 bytes from 192.168.100.27: icmp_seq=3451 ttl=64 time=174.539 ms 64 bytes from 192.168.100.27: icmp_seq=3452 ttl=64 time=97.925 ms 64 bytes from 192.168.100.27: icmp_seq=3453 ttl=64 time=2.434 ms 64 bytes from 192.168.100.27: icmp_seq=3454 ttl=64 time=2.345 ms 64 bytes from 192.168.100.27: icmp_seq=3455 ttl=64 time=2.877 ms 64 bytes from 192.168.100.27: icmp_seq=3456 ttl=64 time=2.211 ms 64 bytes from 192.168.100.27: icmp_seq=3457 ttl=64 time=17.703 ms 64 bytes from 192.168.100.27: icmp_seq=3458 ttl=64 time=5.383 ms 64 bytes from 192.168.100.27: icmp_seq=3459 ttl=64 time=2.192 ms 64 bytes from 192.168.100.27: icmp_seq=3460 ttl=64 time=18.042 ms 64 bytes from 192.168.100.27: icmp_seq=3461 ttl=64 time=2.464 ms 64 bytes from 192.168.100.27: icmp_seq=3462 ttl=64 time=8.449 ms 64 bytes from 192.168.100.27: icmp_seq=3463 ttl=64 time=2.330 ms 64 bytes from 192.168.100.27: icmp_seq=3464 ttl=64 time=7.009 ms 64 bytes from 192.168.100.27: icmp_seq=3465 ttl=64 time=2.058 ms
One case see that the pings are fluctuating a lot, AND there are periods where the device doesn't respond. All the while, it was open & unlocked. Here's the summary:
3850 packets transmitted, 2811 packets received, 27.0% packet loss round-trip min/avg/max/stddev = 1.604/1071.133/37034.517/4097.303 ms
I've tried the following to remedy this:
- Removed the other PoE devices from the switch, to see if it was overloaded. Made no difference.
- Added the PoE injector to the AP. Made no difference.
- Changed wifi channels for the 2.4GHz radio. This is the best I could get it: 
(Since taking this screenshot a few minutes ago, the 2.4GHz utilisation has jumped to 28%. Coincidence?)
I'm rather stumped. Does anyone have any suggestions?
