From nobody Sat Apr 30 07:46:47 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 1A79C1AB9C1D; Sat, 30 Apr 2022 07:46:57 +0000 (UTC) (envelope-from SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kr1dq5DVtz4WT1; Sat, 30 Apr 2022 07:46:55 +0000 (UTC) (envelope-from SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl) Date: Sat, 30 Apr 2022 09:46:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1651304808; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=l1Okte1UTIa/eeJqNPTCsE/3yRNgKLvydqpw9uhxqRQ=; b=jtqVR+Z70fQMx4A5jyQhDmChw8ItL8+/10yb2A45ucBOSDGxsXBohArVFOBD6FCJVSU+wq GL/nEUwpYtnIKlEMBpAkQLt1q6OJWcewXDPC8lgTk7c1KoQkdSlgSPBgkRGxYqTYMTg35P amRinbRmlOoLGULgXw8UezDF/fkKXVsyqBAI79dfLWMtStVawfo8EkmITMNKAjU2t3YZCK 3X82FnEPlC+XiMZzML7tmPIiyZhtn3raIW6p8T7UUkh0YvMQTXKwdn0gurtXFhdkePaI4k OFHke2T6IWj1qz/W8SbwExCM85A8yyARgkZD587EdG4x4s2glGNikH3DCe13aw== From: Ronald Klop To: freebsd-net@freebsd.org, freebsd-arm@freebsd.org, bob prohaska Message-ID: <911244865.14233.1651304807669@localhost> In-Reply-To: <20220430021207.GA7600@www.zefox.net> Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 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: multipart/alternative; boundary="----=_Part_14232_2027219218.1651304807667" X-Mailer: Realworks (604.85.e688255) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4Kr1dq5DVtz4WT1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=jtqVR+Z7; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-1.23 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_SPAM_SHORT(0.96)[0.961]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; HAS_X_PRIO_THREE(0.00)[3]; MLMMJ_DEST(0.00)[freebsd-arm,freebsd-net]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_NOT_FQDN(0.50)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=Z1EM=VI=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_14232_2027219218.1651304807667 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, Did you swap cables? Regards, Ronald Van: bob prohaska Datum: 30 april 2022 04:13 Aan: freebsd-net@freebsd.org, freebsd-arm@freebsd.org CC: bob prohaska Onderwerp: Re: 60+% ping packet loss on Pi3 under -current and stable-13 > > > 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 > > > > > > > ------=_Part_14232_2027219218.1651304807667 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

Did you swap cables?

Regards,
Ronald

Van: bob prohaska <fbsd@www.zefox.net>
Datum: 30 april 2022 04:13
Aan: freebsd-net@freebsd.org, freebsd-arm@freebsd.org
CC: bob prohaska <fbsd@www.zefox.net>
Onderwerp: Re: 60+% ping packet loss on Pi3 under -current and stable-13

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
  





------=_Part_14232_2027219218.1651304807667--