Date: Wed, 30 Dec 2020 08:04:03 +0100 From: "Hartmann, O." <o.hartmann@walstatt.org> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: # Fssh_packet_write_wait: Connection to 77.183.250.3 port 22: Broken pipe Message-ID: <20201230080403.5474da7c@hermann.fritz.box>
next in thread | raw e-mail | index | archive | help
--Sig_/DiADLrU_uOTwhhtOoPsJdUZ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty proble= m which occured a while ago after it seemed to have vanished for a while: running s= sh in a xterm on FreeBSD boxes as mentioned at the beginning ends up very rapidly in a lo= st connection with # 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-ST= ABLE 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 brok= en pipes occured, but not that frequent and rapid as it is the fact now.=20 The "problem" can be mitigated somehow: running top or using the console pr= events 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 oc= cur. 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). Access= ing clients are recent GhostBSD or FreeBSD 12.2-RELENG, utilizing Remmina (port sysutil= s/remmina). It doesn't matter whether I take the ports from our local poudriere driven rep= ository or from one of the official ones. SSH via Remmina dies the same death as it do= es on all customized boxes. And those failing scenarios are occur in all kind of netw= orks, 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 offic= ial repository running unchanged. Kind regards, oh --Sig_/DiADLrU_uOTwhhtOoPsJdUZ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCX+wmYwAKCRA4N1ZZPba5 R3+vAP9dBTPFgp/dBE9pWSKqaRupoIwOrI+IjwxmETthoQpGqQEAk/Io4jDycZpb yr54Ths7aMLmOobdxrK/isLyB8BzZwM= =Aeg4 -----END PGP SIGNATURE----- --Sig_/DiADLrU_uOTwhhtOoPsJdUZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201230080403.5474da7c>