me_tomas
Contributor
Contributor

Regression: ssh results in broken pipe upon connecting in Vmware Workstation pro

Environment: Fedora 28 as VM in VMware Workstation Pro 14

After a recent upgrade of openssh to version 7.8 ssh connections are not longer working as expected. This does not happen with a native Fedora instance.

    packet_write_wait: Connection to XXXX port 22: Broken pipe

The cause for this seems to come from a change introduced in openssh 7.8 listed under potentially incompatible changes: (from OpenSSH 7.8 released [LWN.net] )

* ssh(1)/sshd(8): the default IPQoS used by ssh/sshd has changed.

   They will now use DSCP AF21 for interactive traffic and CS1 for

   bulk.  For a detailed rationale, please see the commit message:

   https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh...

References:

Bug 1624437 – 7.8p1-1.fc28 breaks ssh connections to other systems when client is running on VMware ...

For me, this happens both in NAT and bridged mode.

Please fix this issue.

Tags (2)
8 Replies
yanw
VMware Employee
VMware Employee

We have observed the issue for NAT mode, are you sure your openssh 7.8 has the same issue for bridge mode?

me_tomas
Contributor
Contributor

I had to re-test in bridged mode. Indeed, it seems to be working correctly in bridged mode.

0 Kudos
Olaf_van_der_Sp
Enthusiast
Enthusiast

What's the status of this bug?

Sinorama
Enthusiast
Enthusiast

Still need work around in sshd_config (IPQoS=lowdelay throughput) in WS pro 15.02 for nat port forward to openssh 7.9p1.

Definitely something wrong with VMware nat and openssh 7.9p1. When I test with another router, nat port forward works without change to sshd_config.

Is there a bug report opened?

0 Kudos
JuhaZ
Contributor
Contributor

Just hit this issue and spend way too much time to track this down. VMware, please address this!

Quick workaround from command line is to use

ssh -o IPQoS=0x10 user@host

0 Kudos
DazzaFG
Contributor
Contributor

Bump! this affects me too. I hope it will be fixed soon.

0 Kudos
lcarsos
Contributor
Contributor

This is still an issue in the latest Fusion Pro (11.0.3 12992109) also. Very frustrating as I can't use the bridged networking workaround when on my work's VPN.

0 Kudos
lcarsos
Contributor
Contributor

I believe this has been fixed in Fusion Pro 11.1.0 (13668589).

0 Kudos