Date: Sat, 30 Apr 2022 09:46:47 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: freebsd-net@freebsd.org, freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: 60+% ping packet loss on Pi3 under -current and stable-13 Message-ID: <911244865.14233.1651304807669@localhost> In-Reply-To: <20220430021207.GA7600@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_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 <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 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body>Hi,<div><br /></div><div>Did you swap cables?</div><div><br /></div><div>Regards,</div><div>Ronald</div><div><br /><p><small><strong>Van:</strong> bob prohaska <fbsd@www.zefox.net><br /><strong>Datum:</strong> 30 april 2022 04:13<br /><strong>Aan:</strong> freebsd-net@freebsd.org, freebsd-arm@freebsd.org<br /><strong>CC:</strong> bob prohaska <fbsd@www.zefox.net><br /><strong>Onderwerp:</strong> Re: 60+% ping packet loss on Pi3 under -current and stable-13<br /></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->Since about December of 2021 I've been noticing problems with<br /> wired network connectivity on a pair of raspberry pi 3 machines<br /> using wired network connections. One runs stable-13.1, the other<br /> runs -current, both are up to date as of a few days ago.<br /> <br /> Essentially both machines fail to respond to inbound network<br /> connections via ssh or ping after reboot. If I get on the <br /> serial console and start an outbound ping to anywhere, both<br /> machines respond to incoming pings with about a 65% packet<br /> loss. Ssh connections are answered with delays of zero to<br /> perhaps thirty seconds. Once connected ssh is usable but<br /> erratic, with dropped characters, multi-second delays and<br /> disconnects after random intervals from minutes to hours.<br /> <br /> There are five other Raspberry Pi's on the network. Three<br /> Pi2's run 12.3-stable, one Pi2 runs -current and a Pi4 runs<br /> -current. All have no problems pinging one another and out<br /> of network, so there's nothing obviously wrong with the net.<br /> The network is not routed, but rather a block of eight<br /> addresses simply bridged from my ISP over DSL.<br /> <br /> It's been found that an image of 13.1-RC4 behaves similarly<br /> on one Pi3 when on the public network but exhibits more normal<br /> ping response when moved to a 192.168.1.n private network. On<br /> the face of it, this seems significant, but I can't guess how.<br /> <br /> I recall a post on one of the mailing lists about a bug that<br /> caused problems when packets arrived out-of-order via NAT, <br /> but I'm using direct same-network pings and pinging through <br /> NAT seems little-to-no worse.<br /> <br /> I was hoping to upgrade my stable-12 machines to stable-13,<br /> but seeing this behavior gives me pause. If anyone can <br /> suggest tests or experiments to figure out what's going on<br /> I'd be most grateful. I'm no programmer but can follow <br /> simple instructions. If this sounds like a known bug(s)<br /> links to bugzilla would be of much interest.<br /> <br /> Many thanks for reading, and any ideas! If some essential<br /> details have been omitted please indicate and I'll try to<br /> supply them. <br /> <br /> bob prohaska<br /> <br /> <br /> <br /> </div><!-- TextPlainViewer --> <hr /> </div><!-- MessageRFC822Viewer --> </blockquote><br /><br /><br /></div></body></html> ------=_Part_14232_2027219218.1651304807667--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?911244865.14233.1651304807669>