what's a channel survey give? is it on a very busy channel? Is there a nearby device?
-a On Wed, 21 Nov 2018 at 07:28, Volodymyr Kostyrko <arc...@b1t.name> wrote: > On 16.11.18 00:02, Adrian Chadd wrote: > > ok, interesting. I'll see if I can reproduce it later next week. I > haven't > > changed much on the AR9220 HAL... > > Though I'm already not quite sure that's about wireless: > > Client side: > > 64 bytes from 172.29.1.1: icmp_seq=3484 ttl=64 time=6769.941 ms > 64 bytes from 172.29.1.1: icmp_seq=3485 ttl=64 time=5759.887 ms > 64 bytes from 172.29.1.1: icmp_seq=3486 ttl=64 time=4749.831 ms > 64 bytes from 172.29.1.1: icmp_seq=3491 ttl=64 time=1079.225 ms > ping: sendto: Network is down > ping: sendto: Network is down > 64 bytes from 172.29.1.1: icmp_seq=3543 ttl=64 time=3.459 ms > 64 bytes from 172.29.1.1: icmp_seq=3544 ttl=64 time=0.765 ms > 64 bytes from 172.29.1.1: icmp_seq=3545 ttl=64 time=0.764 ms > > Server side: > > 17:16:13.780615 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3484, length 64 > 17:16:13.780626 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3484, length 64 > 17:16:13.780665 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3485, length 64 > 17:16:13.780671 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3485, length 64 > 17:16:13.780798 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3486, length 64 > 17:16:13.780806 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3486, length 64 > 17:16:13.901127 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 1209 unreachable, length 36 > 17:16:13.926867 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 1209 unreachable, length 36 > 17:16:13.926901 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 2265 unreachable, length 36 > 17:16:13.953174 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 2265 unreachable, length 36 > 17:16:14.255022 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3491, length 64 > 17:16:14.255043 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3491, length 64 > 17:16:14.666831 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 1549 unreachable, length 36 > 17:16:14.666847 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 1191 unreachable, length 36 > 17:16:14.666853 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port > 1626 unreachable, length 36 > 17:16:15.268339 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3492, length 64 > 17:16:15.268376 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3492, length 64 > 17:16:16.292245 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3493, length 64 > 17:16:16.292265 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3493, length 64 > 17:16:17.326008 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3494, length 64 > 17:16:17.326050 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3494, length 64 > 17:16:18.306333 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3495, length 64 > 17:16:18.306349 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3495, length 64 > 17:16:19.305307 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3496, length 64 > 17:16:19.305341 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3496, length 64 > 17:16:20.316914 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3497, length 64 > 17:16:20.316951 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3497, length 64 > 17:16:21.358600 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3498, length 64 > 17:16:21.358627 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3498, length 64 > 17:16:22.667213 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id > 61963, seq 3499, length 64 > 17:16:22.667240 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, > seq 3499, length 64 > > 1. Everything works. > 2. Packets 3487 - 3490 doesn't reach server. > 3. Packet 3491 hits. > 4. Packets 3492 - 3540 doesn't reach client. > 5. I frob the client link. > 6. 2 packets went nowhere while connection gets established. > 7. Everything works. > > No bstuck increments in the process. > > -- > Sphinx of black quartz judge my vow. > _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
