From nobody Sat Apr 30 02:12:07 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A4D8919961B0; Sat, 30 Apr 2022 02:12:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KqtCg2fd4z3CnF; Sat, 30 Apr 2022 02:12:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 23U2C7R6007680 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 29 Apr 2022 19:12:08 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 23U2C7Mi007679; Fri, 29 Apr 2022 19:12:07 -0700 (PDT) (envelope-from fbsd) Date: Fri, 29 Apr 2022 19:12:07 -0700 From: bob prohaska To: freebsd-net@freebsd.org, freebsd-arm@freebsd.org Cc: bob prohaska Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 Message-ID: <20220430021207.GA7600@www.zefox.net> References: <8936EFD1-F1FD-48CF-9ED3-4D42595464DC@yahoo.com> <20220313193406.GA65568@www.zefox.net> <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> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4KqtCg2fd4z3CnF X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-net,freebsd-arm]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N 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. I recall a post on one of the mailing lists about a bug that caused problems when packets arrived out-of-order via NAT, but I'm using direct same-network pings and pinging through NAT seems little-to-no worse. I was hoping to upgrade my stable-12 machines to stable-13, but seeing this behavior gives me pause. If anyone can suggest tests or experiments to figure out what's going on I'd be most grateful. I'm no programmer but can follow simple instructions. If this sounds like a known bug(s) links to bugzilla would be of much interest. Many thanks for reading, and any ideas! If some essential details have been omitted please indicate and I'll try to supply them. bob prohaska