Date: Mon, 2 May 2022 00:44:48 -0700 From: Bakul Shah <bakul@iitbombay.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-net@freebsd.org, freebsd-arm@freebsd.org Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 Message-ID: <82F25CEE-9C9C-4CCD-9A59-A4448C37DA95@iitbombay.org> In-Reply-To: <20220501181254.GA14961@www.zefox.net> References: <D0DFF445-9B68-4C64-B9CA-D68149ACD89E@yahoo.com> <20220314010330.GA70447@www.zefox.net> <9FA3F874-2987-44A2-A987-F905E78CCA65@yahoo.com> <20220428023226.GA5666@www.zefox.net> <8A57B411-AA06-47F4-935D-EDF45D8DF0EC@yahoo.com> <70C2DF4B-D08B-491D-B7B5-1EAD0D1BF0E3@yahoo.com> <20220429005206.GA1171@www.zefox.net> <A5172CAE-7327-4B13-94F7-989607D01237@yahoo.com> <20220430021207.GA7600@www.zefox.net> <FE6B7DD6-4F71-430C-A78D-480D18F45CCA@iitbombay.org> <20220501181254.GA14961@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 1, 2022, at 11:12 AM, bob prohaska <fbsd@www.zefox.net> wrote: > The "oui unknown" looks like some sort of failure..... Just ignore. tcpdump couldn't identify the vendor. Your tcpdump trace didn't give me anything useful. One suggestion is to use -n flag so that tcpdump doesn't do DNS resolution! Better, just use "-w file" so that you capture a trace and then can filter it different ways along with "-r file". Create separate files for when connected to the public vs private net. > Can you ping www.zefox.org? I have no outside vantage point. > There is still no outbound ping running and I would expect > you'll get no or very sparse reply. Looks like you are a sonic.net customer? If so see if you can get shell access on sonic. Then you can ping your hosts "from the outside"! Earlier I saw some packet loss. Right now I don't see any. > Thus far only the two Pi3s suffer from connectivity problems; Pi2s and = a Pi4 have > no difficulty on the same address block. Is there a switch for tcpdump = that will > limit records to relevant traffic? Otherwise it's a flood. When see packet loss, do you see any IO errors when you do "netstat -ni ue0"? Also check if your resolv.conf is set right as well as your gateway. > These results were obtained after standing idle overnight and > are rather different (in ways I don't understand) from behavior > immediately after reboot, I'll have to repeat as I learn more. >=20 > Thanks for reading, and any more suggestions! >=20 > bob prohaska >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82F25CEE-9C9C-4CCD-9A59-A4448C37DA95>