Date: Thu, 5 May 2022 09:21:20 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Hans Petter Selasky <hps@selasky.org> Cc: Bakul Shah <bakul@iitbombay.org>, freebsd-net@freebsd.org Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 Message-ID: <20220505162120.GA30539@www.zefox.net> In-Reply-To: <20220504154125.GA26674@www.zefox.net> References: <CA5CAD79-F2B6-464D-978A-B9FFC8D2125A@yahoo.com> <20220501232757.GA15446@www.zefox.net> <2F4599BF-EEDA-4D08-AB6E-7AA9F410B2C5@yahoo.com> <20220502011312.GA15807@www.zefox.net> <6f57cd1d-e1d4-5ca4-e301-2633c1d4c1fa@selasky.org> <20220502155334.GA17962@www.zefox.net> <D400ADAB-9EB3-4CA1-8746-A378F9878B6A@iitbombay.org> <0d131ec7-3c83-9470-7052-6a80af1bb574@selasky.org> <20220503022310.GA19378@www.zefox.net> <20220504154125.GA26674@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The -current Pi3 that's having ping trouble behaves sligtly differently compared to the stable-13 example. A one-hop (no NAT) ping looks like: [test host is rebooting] ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down 64 bytes from 50.1.20.28: icmp_seq=35 ttl=64 time=52.568 ms [ue0 just came up] 64 bytes from 50.1.20.28: icmp_seq=49 ttl=64 time=4.663 ms 64 bytes from 50.1.20.28: icmp_seq=51 ttl=64 time=1.044 ms [ntp set time] [I started outbound ping. Should have waited a bit longer.] 64 bytes from 50.1.20.28: icmp_seq=53 ttl=64 time=0.929 ms 64 bytes from 50.1.20.28: icmp_seq=55 ttl=64 time=0.902 ms 64 bytes from 50.1.20.28: icmp_seq=80 ttl=64 time=1.140 ms 64 bytes from 50.1.20.28: icmp_seq=81 ttl=64 time=1.064 ms 64 bytes from 50.1.20.28: icmp_seq=88 ttl=64 time=1.070 ms 64 bytes from 50.1.20.28: icmp_seq=108 ttl=64 time=0.967 ms 64 bytes from 50.1.20.28: icmp_seq=109 ttl=64 time=0.911 ms 64 bytes from 50.1.20.28: icmp_seq=110 ttl=64 time=0.913 ms ^C --- www.zefox.org ping statistics --- 112 packets transmitted, 11 packets received, 90.2% packet loss round-trip min/avg/max/stddev = 0.902/6.016/52.568/14.759 ms [no explicit errors on console] Uname -a on the test host reports FreeBSD 14.0-CURRENT #58 main-n255160-9a3583bfbd1: Wed May 4 21:47:21 PDT 2022 bob@www.zefox.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC Am I correct in thinking that "main-n255160" is a sort of serial number that can be used to compare branch revisions by age? Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220505162120.GA30539>