workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes
imp at bsdimp.com
Sat Dec 22 00:19:20 UTC 2018
I've been hit by this as well. At least two others on IRC have had the same
On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper <yaneurabeya at gmail.com> wrote:
> > On Dec 21, 2018, at 3:55 PM, Yuri Pankov <yuripv at yuripv.net> wrote:
> > Hi,
> > There's apparently a bug in VMware Workstation NAT implementation, made
> > visible by the change to default values of IPQoS in OpenSSH 7.8p1,
> > making all ssh connections from the guest behind the NAT to fail with
> > obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22:
> > Broken pipe".
> > I wonder if we could integrate the attached patch (or some smarter
> > version of it) for the time being as the bug affects several major WS
> > releases, and it's not immediately clear where the problem is.
> > The change itself:
> > The bug reports (some of them):
> > https://bugzilla.redhat.com/show_bug.cgi?id=1624437
> > https://communities.vmware.com/message/2803219#2803219
> > The patch itself is attached.
> > <vmwssh.diff>
> Cool… yeah… I’ve been running into this issue for a while with
> VMware Fusion 11.0.1.
> I CCed mp@ for visibility.
More information about the freebsd-current