Date: Wed, 30 Dec 2020 14:14:48 +0100 From: "Hartmann, O." <o.hartmann@walstatt.org> To: Michael Tuexen <Michael.Tuexen@macmic.franken.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: # Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe Message-ID: <20201230141448.48871cc5@hermann.fritz.box> In-Reply-To: <F020BEC8-C3B4-41E7-B4E9-5ECC93E6E762@macmic.franken.de> References: <20201230080403.5474da7c@hermann.fritz.box> <F020BEC8-C3B4-41E7-B4E9-5ECC93E6E762@macmic.franken.de>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, 30 Dec 2020 12:13:44 +0100 Michael Tuexen <Michael.Tuexen@macmic.franken.de> wrote: > On 30. Dec 2020, at 08:04, Hartmann, O. <o.hartmann@walstatt.org> wrote: > > > > On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty problem which > > occured a while ago after it seemed to have vanished for a while: running ssh in a > > xterm on FreeBSD boxes as mentioned at the beginning ends up very rapidly in a lost > > connection with > How can I reproduce the problem? Just ssh'ing into a server? Client and server running > FreeBSD head? Are there middleboxes (NAT, Firewall) involved or does it also happen if > client and server are directly connected? What does 'rapidly' mean: 1 second, 1 minute, > 1 hour, 1 day? Take this course: 12-STABLE (FreeBSD 12.2-STABLE #63 r368787+3cc3872829b1(stable/12): Mon Dec 28 06:07:57 CET 2020 amd64). As a target (server) I just used a LibreELEC box, Leia 18. something, core 9.2.6. My notebook this time is a Lenovo E540. ssh is running in xterm. After a successful login on the KODI/LibreElec, wait for a couple of minutes. It is random, the session of mine died after 2 to 5 minutes of idling, one can extend that timeframe by starting top on the KODI/shell. regards oh p.s. That is only one scenario that I faced at home just a couple of minutes ago. > > Best regards > Michael > > > > # Fssh_packet_write_wait: Connection to XXX.XXX.XXX.XXX port 22: Broken pipe > > > > The backend is in most cases a CURRENT, 12.1-RELENG or 12.2-RELENG or 12-STABLE > > server. A couple of months ago we moved from 11.3-RELENG to 12.1-RELENG (server side, > > clients were always 13-CURRENT or 12-STABLE). With FreeBSD 11 as the backend, those > > broken pipes occured, but not that frequent and rapid as it is the fact now. > > > > The "problem" can be mitigated somehow: running top or using the console prevents the > > broken pipe fault for a while, but it still occurs. Running "screen" (port > > sysutils/screen) does extend the usability of the console for a significant timespan, > > but the broken pipe also occurs randomly, but it takes a significant time to occur. > > > > All systems mentioned above are highly customized, so I used the chance of another, > > more "generic" scenario to test. The backend is a most recent Xigmanas machine > > (running Hardened FreeBSD 12, latest official issue, its based on FBSD 12.1). > > Accessing clients are recent GhostBSD or FreeBSD 12.2-RELENG, utilizing Remmina (port > > sysutils/remmina). It doesn't matter whether I take the ports from our local > > poudriere driven repository or from one of the official ones. SSH via Remmina dies > > the same death as it does on all customized boxes. And those failing scenarios are > > occur in all kind of networks, home-ISP-lab/work, lab's network, home's network with > > foreign, Linux based CPE or other vendor's CPE. > > > > My conclusion is: either there is a serious problem with FreeBSD since 12, or there > > is a config issue I'm not aware of, even with "vanilla" installations from official > > repository running unchanged. > > > > Kind regards, > > > > oh > [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCX+x9SAAKCRA4N1ZZPba5 R9HTAQCoylYTmyy5Canw0uTU7uiFMX3cJ9CcnnKGK8toVecKPgD9GYsrKkneZ32J BoBX7imznEGT5Su4CsIeqStztzeKJQk= =aQLR -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201230141448.48871cc5>