Date: Wed, 27 Apr 2022 22:04:27 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Erratic ping behavior, was Re: Pi3 answers ssh only if outbound ping is running on -current Message-ID: <8A57B411-AA06-47F4-935D-EDF45D8DF0EC@yahoo.com> In-Reply-To: <20220428023226.GA5666@www.zefox.net> References: <8F9A6C9A-69BF-4D42-9886-A3F08BCB2EA0@yahoo.com> <506CD1A7-3D34-4E1B-AEAA-A1A819C6CC73@yahoo.com> <B186B406-233A-4765-9B1B-EB8136D01F2B@yahoo.com> <20220216231826.GA54961@www.zefox.net> <64138E81-2415-4D4A-A31A-D901DC53EB01@yahoo.com> <8936EFD1-F1FD-48CF-9ED3-4D42595464DC@yahoo.com> <20220313193406.GA65568@www.zefox.net> <D0DFF445-9B68-4C64-B9CA-D68149ACD89E@yahoo.com> <20220314010330.GA70447@www.zefox.net> <9FA3F874-2987-44A2-A987-F905E78CCA65@yahoo.com> <20220428023226.GA5666@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Apr-27, at 19:32, bob prohaska <fbsd@www.zefox.net> wrote: > On Sun, Mar 13, 2022 at 09:45:02PM -0700, Mark Millard wrote: >> >> A point of testing is to compare/contrast different contexts >> instead of guessing about the alternatives. If the test >> that I proposed showed the failure, it would disprove your >> hypothesis --and it that happened it would be good to know. >> > > You're correct, as usual.... > > I just tried booting the 13.1-RC4 candidate on my Pi3 from > microSD. It exhibits the same strange "no response to inbound > ping" as before. It does seem to set time successfully using > ntp, and outbound ping works fine. > > Inbound ping from both the same (public) network and across > a NAT link from my LAN work very poorly. The NAT'd link shows > 92% packet loss, the direct link around 88% loss. > > The USB devices present are an FTDI232 and an ASMT usb-sata > bridge, neither is in active use. > > Inbound ssh connections time out, even with outbound ping > running and getting answers. Not even a password prompt. > > It's hard to believe I'm the only one seeing this...... RPi3B? RPi3B+? Which Rev? So, if I gather correctly, if I expand: FreeBSD-13.1-RC4-arm64-aarch64-RPI.img.xz onto an microsd card, boot an RPi3B with EtherNet plugged in, and test pinging to it, I will have replicated your context except for, possibly: A) RPi3B exact Model/Revision B) presence of a FTDI232 plugged into a USB2 port C) presence of a ASMT usb-sata bridge plugged into a USB2 port (no drive?) D) the details of the EtherNet network that I'd being using. (No public network or NAT in the path between machines [same local subnet, no other local subnets present], just a simple local switch, the cables, the RPi3B, whatever other computer(s) I use, and the device that provides DHCP assignments for the network.) If true, I can try such. But to get to a matching test, you would have to deal with eliminating (B-C) from the context and setting up something like (D) as the networking context. (Seems more reasonable than me trying to replicate your public network/NAT context.) Note: I would normally have a serial port connected to the proper pins for having a boot console. Once I prove I have correctly set up/booting microsd card media context, I could eliminate that. (The other end is USB but that is not what the RPi3B is connected to.) === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A57B411-AA06-47F4-935D-EDF45D8DF0EC>