Hi, It seems I'm still seeing issues with packet loss, spikes in latency, and TX excessive retries. [hloeung@darkon tmp]$ ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=3.16 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.28 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=6.11 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=1634 ms 64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=762 ms 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=7.41 ms 64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=3.03 ms 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=3.26 ms 64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=3.31 ms 64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=5.84 ms 64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=6.15 ms 64 bytes from 192.168.2.1: icmp_seq=19 ttl=64 time=8.55 ms 64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=5.69 ms 64 bytes from 192.168.2.1: icmp_seq=21 ttl=64 time=3.82 ms 64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=1962 ms 64 bytes from 192.168.2.1: icmp_seq=25 ttl=64 time=1012 ms 64 bytes from 192.168.2.1: icmp_seq=26 ttl=64 time=5.96 ms 64 bytes from 192.168.2.1: icmp_seq=27 ttl=64 time=3.02 ms 64 bytes from 192.168.2.1: icmp_seq=28 ttl=64 time=3.54 ms 64 bytes from 192.168.2.1: icmp_seq=29 ttl=64 time=3.22 ms 64 bytes from 192.168.2.1: icmp_seq=30 ttl=64 time=7.55 ms 64 bytes from 192.168.2.1: icmp_seq=31 ttl=64 time=3.26 ms 64 bytes from 192.168.2.1: icmp_seq=32 ttl=64 time=2.99 ms 64 bytes from 192.168.2.1: icmp_seq=34 ttl=64 time=2297 ms 64 bytes from 192.168.2.1: icmp_seq=35 ttl=64 time=1289 ms 64 bytes from 192.168.2.1: icmp_seq=36 ttl=64 time=281 ms 64 bytes from 192.168.2.1: icmp_seq=37 ttl=64 time=5.25 ms 64 bytes from 192.168.2.1: icmp_seq=38 ttl=64 time=2.28 ms 64 bytes from 192.168.2.1: icmp_seq=39 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=40 ttl=64 time=3.22 ms 64 bytes from 192.168.2.1: icmp_seq=41 ttl=64 time=3.26 ms 64 bytes from 192.168.2.1: icmp_seq=42 ttl=64 time=7.46 ms 64 bytes from 192.168.2.1: icmp_seq=43 ttl=64 time=6.18 ms ^C --- 192.168.2.1 ping statistics --- 43 packets transmitted, 39 received, 9% packet loss, time 42088ms rtt min/avg/max/mdev = 2.280/240.515/2297.437/575.005 ms, pipe 3 [hloeung@darkon tmp]$ iwconfig lo no wireless extensions. wlan0 IEEE 802.11abgn ESSID:"star-local" Mode:Managed Frequency:2.452 GHz Access Point: 00:22:75:29:EC:61 Bit Rate=135 Mb/s Tx-Power=15 dBm Retry limit:0 RTS thr:off Fragment thr:off Power Management:on Link Quality=54/70 Signal level=-56 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:5517 Invalid misc:25 Missed beacon:0 This is happening on more than one AP from different manufacturers (Belkin and AVM FRITZ!). I've been running with 802.11n disabled but having read LP: #836250 and LP: #1201470, I thought I'd try re-enable 802.11n again. Running saucy beta 1. [hloeung@darkon tmp]$ uname -a Linux darkon 3.11.0-7-generic #13-Ubuntu SMP Tue Sep 10 20:55:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux