Re: Erratic ping behavior, was Re: Pi3 answers ssh only if outbound ping is running on -current

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