Well, I just rebooted to a new snapshot, and WiFi has been future degradated.
I do run a MPD sync in background which downloads some files via HTTP, but I may run before, and it never creates an issue. Meanwhile the ping to GW from latop seems like: ~ $ ping 172.31.2.1 PING 172.31.2.1 (172.31.2.1): 56 data bytes 64 bytes from 172.31.2.1: icmp_seq=0 ttl=64 time=36.148 ms 64 bytes from 172.31.2.1: icmp_seq=1 ttl=64 time=50.701 ms 64 bytes from 172.31.2.1: icmp_seq=2 ttl=64 time=65.322 ms 64 bytes from 172.31.2.1: icmp_seq=3 ttl=64 time=46.276 ms 64 bytes from 172.31.2.1: icmp_seq=4 ttl=64 time=58.030 ms 64 bytes from 172.31.2.1: icmp_seq=5 ttl=64 time=34.199 ms 64 bytes from 172.31.2.1: icmp_seq=6 ttl=64 time=47.096 ms 64 bytes from 172.31.2.1: icmp_seq=7 ttl=64 time=40.565 ms ping: sendmsg: No buffer space available ping: wrote 172.31.2.1 64 chars, ret=-1 64 bytes from 172.31.2.1: icmp_seq=9 ttl=64 time=44.815 ms 64 bytes from 172.31.2.1: icmp_seq=10 ttl=64 time=33.036 ms 64 bytes from 172.31.2.1: icmp_seq=11 ttl=64 time=63.137 ms 64 bytes from 172.31.2.1: icmp_seq=12 ttl=64 time=41.274 ms 64 bytes from 172.31.2.1: icmp_seq=13 ttl=64 time=59.496 ms 64 bytes from 172.31.2.1: icmp_seq=14 ttl=64 time=48.939 ms ping: sendmsg: No buffer space available ping: wrote 172.31.2.1 64 chars, ret=-1 64 bytes from 172.31.2.1: icmp_seq=16 ttl=64 time=44.050 ms 64 bytes from 172.31.2.1: icmp_seq=17 ttl=64 time=40.177 ms ping: sendmsg: No buffer space available ping: wrote 172.31.2.1 64 chars, ret=-1 64 bytes from 172.31.2.1: icmp_seq=19 ttl=64 time=62.400 ms 64 bytes from 172.31.2.1: icmp_seq=20 ttl=64 time=40.147 ms ^C --- 172.31.2.1 ping statistics --- 21 packets transmitted, 18 packets received, 14.3% packet loss round-trip min/avg/max/std-dev = 33.036/47.545/65.322/9.949 ms ~ $ Between AP and GW is 1Gb network, and my laptop in 50cm from AP. I've tried to reboot AP, it doesn't help but move from 5Ghz to 2.4Ghz helps, and on 5Ghz it is: ~ $ ping 172.31.2.1 PING 172.31.2.1 (172.31.2.1): 56 data bytes 64 bytes from 172.31.2.1: icmp_seq=0 ttl=64 time=518.499 ms 64 bytes from 172.31.2.1: icmp_seq=1 ttl=64 time=459.383 ms 64 bytes from 172.31.2.1: icmp_seq=2 ttl=64 time=787.812 ms 64 bytes from 172.31.2.1: icmp_seq=3 ttl=64 time=471.442 ms 64 bytes from 172.31.2.1: icmp_seq=4 ttl=64 time=493.617 ms 64 bytes from 172.31.2.1: icmp_seq=5 ttl=64 time=856.977 ms 64 bytes from 172.31.2.1: icmp_seq=6 ttl=64 time=735.358 ms 64 bytes from 172.31.2.1: icmp_seq=7 ttl=64 time=1012.529 ms 64 bytes from 172.31.2.1: icmp_seq=8 ttl=64 time=1591.216 ms 64 bytes from 172.31.2.1: icmp_seq=9 ttl=64 time=591.264 ms 64 bytes from 172.31.2.1: icmp_seq=10 ttl=64 time=374.638 ms 64 bytes from 172.31.2.1: icmp_seq=11 ttl=64 time=561.372 ms 64 bytes from 172.31.2.1: icmp_seq=12 ttl=64 time=344.401 ms 64 bytes from 172.31.2.1: icmp_seq=13 ttl=64 time=397.568 ms 64 bytes from 172.31.2.1: icmp_seq=14 ttl=64 time=375.690 ms 64 bytes from 172.31.2.1: icmp_seq=15 ttl=64 time=484.299 ms 64 bytes from 172.31.2.1: icmp_seq=16 ttl=64 time=239.776 ms 64 bytes from 172.31.2.1: icmp_seq=17 ttl=64 time=353.970 ms 64 bytes from 172.31.2.1: icmp_seq=18 ttl=64 time=183.788 ms 64 bytes from 172.31.2.1: icmp_seq=19 ttl=64 time=569.264 ms 64 bytes from 172.31.2.1: icmp_seq=20 ttl=64 time=449.187 ms 64 bytes from 172.31.2.1: icmp_seq=21 ttl=64 time=289.776 ms 64 bytes from 172.31.2.1: icmp_seq=22 ttl=64 time=412.872 ms ping: sendmsg: No buffer space available ping: wrote 172.31.2.1 64 chars, ret=-1 64 bytes from 172.31.2.1: icmp_seq=25 ttl=64 time=138.947 ms 64 bytes from 172.31.2.1: icmp_seq=26 ttl=64 time=359.616 ms 64 bytes from 172.31.2.1: icmp_seq=27 ttl=64 time=377.133 ms So, latency is much worst. No error, nothing in dmesg since reebot. I'm running on the kernel as it was installed on taday's snapshot. And my home WiFi network is running on Automatic mode from Unifi, without any hacks. -- wbr, Kirill
