OpenSSH 7.8p1 drops SSH connection with "Broken Pipe" IMMEDIATELY after successful login

[Ohad Frenkel]

Yes, thank you!
Now with the "Host *" line it works.

Thanks again.

Sent from BlueMail<http://www.bluemail.me/r?b=13569>
On Aug 29, 2018, at 08:15, Zach Cheung <kuroro.zhang at gmail.com<mailto:kuroro.zhang at gmail.com>> wrote:
Sorry, your problem is related to ssh client not sshd, try to add following config to /etc/ssh/ssh_config or ~/.ssh/config:
Host *
    IPQoS lowdelay throughput


On Wed, Aug 29, 2018 at 1:24 PM Ohad Frenkel < ohadfjunkbox at outlook.com<mailto:ohadfjunkbox at outlook.com>> wrote:
Added the line as above: 'IPQoS lowdelay throughput', restarted the SSH service, tried SSH-ing and Git-ing... same error as before: 'packet_write_wait: Connection to X.X.X.X port 22: Broken pipe'.
________________________________
From: Zach Cheung <kuroro.zhang at gmail.com<mailto:kuroro.zhang at gmail.com>>
Sent: 29 August 2018 07:17
To: ohadfjunkbox at outlook.com<mailto:ohadfjunkbox at outlook.com>
Cc: dtucker at dtucker.net<mailto:dtucker at dtucker.net>; openssh-unix-dev at mindrot.org<mailto:openssh-unix-dev at mindrot.org>
Subject: Re: OpenSSH 7.8p1 drops SSH connection with "Broken Pipe" IMMEDIATELY after successful login

Using for years doesn't mean it won't be its problem, would you try to add ' IPQoS lowdelay throughput' to 7.8p1 sshd_config and check whether fix the problem?

On Wed, Aug 29, 2018 at 1:10 PM Ohad Frenkel < ohadfjunkbox at outlook.com<mailto:ohadfjunkbox at outlook.com>> wrote:
The virtualization is VMware Workstation 12.x, NOT Fusion.
Again, I'd like to point that downgrading to 7.7p2 "solved" the issue and that I'm using the same virtualization software for ages (which makes me disbelieve the issue lies with it).

I've seen the comment about zero-length passwords... I'm not techie enough to understand the code there (or the technical explanation), but it is true that my previous SSH keys were password-less (if that is the meaning of "zero-length password").
I say "previous" because one of the first things I did, trying to solve this on my end, was to assume the problem was with the keys and thus generated a new set of keys, all of which have positive value of characters in the password (which, by the way, did not solve the case. As I said, only downgrading to 7.7p2 did the trick).
________________________________
From: Darren Tucker < dtucker at dtucker.net<mailto:dtucker at dtucker.net>>
Sent: 28 August 2018 22:18
To: Ohad Frenkel
Cc: openssh-unix-dev at mindrot.org<mailto:openssh-unix-dev at mindrot.org>
Subject: Re: OpenSSH 7.8p1 drops SSH connection with "Broken Pipe" IMMEDIATELY after successful login

On 28 August 2018 at 13:36, Ohad Frenkel < ohadfjunkbox at outlook.com<mailto:ohadfjunkbox at outlook.com>> wrote:
>   *   OS: Antergos Linux (Fully updated daily) (Running as a guest on VM).

If the VM host is VMWare Fusion, see
https://lists.mindrot.org/pipermail/openssh-unix-dev/2018-August/037145.html
wherein it appears to have a bug in its networking stack that chokes
on the new default (valid) DSCP markings.  If so you can work around
it by overriding the defaults, but the problem is within VMWare (maybe
in general, or maybe just the Fusion product).

--
Darren Tucker (dtucker at dtucker.net<http://dtucker.net>)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev at mindrot.org<mailto:openssh-unix-dev at mindrot.org>
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev