Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Apr 2022 18:39:57 -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:  <FE6B7DD6-4F71-430C-A78D-480D18F45CCA@iitbombay.org>
In-Reply-To: <20220430021207.GA7600@www.zefox.net>
References:  <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> <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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 29, 2022, at 7:12 PM, bob prohaska <fbsd@www.zefox.net> wrote:
> 
> Since about December of 2021 I've been noticing problems with
> wired network connectivity on a pair of raspberry pi 3 machines
> using wired network connections. One runs stable-13.1, the other
> runs -current, both are up to date as of a few days ago.
> 
> Essentially both machines fail to respond to inbound network
> connections via ssh or ping after reboot. If I get on the 
> serial console and start an outbound ping to anywhere, both
> machines respond to incoming pings with about a 65% packet
> loss. Ssh connections are answered with delays of zero to
> perhaps thirty seconds. Once connected ssh is usable but
> erratic, with dropped characters, multi-second delays and
> disconnects after random intervals from minutes to hours.
> 
> There are five other Raspberry Pi's on the network. Three
> Pi2's run 12.3-stable, one Pi2 runs -current and a Pi4 runs
> -current. All have no problems pinging one another and out
> of network, so there's nothing obviously wrong with the net.
> The network is not routed, but rather a block of eight
> addresses simply bridged from my ISP over DSL.
> 
> It's been found that an image of 13.1-RC4 behaves similarly
> on one Pi3 when on the public network but exhibits more normal
> ping response when moved to a 192.168.1.n private network. On
> the face of it, this seems significant, but I can't guess how.

Suggest running tcpdump on the rpi3 to see what is going on
when connected to the public vs private net. 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FE6B7DD6-4F71-430C-A78D-480D18F45CCA>