Date: Sat, 22 Dec 2018 12:09:17 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Yuri Pankov <yuripv@yuripv.net> Cc: Mark Peek <mp@freebsd.org>, Enji Cooper <yaneurabeya@gmail.com>, Warner Losh <imp@bsdimp.com>, =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= <des@freebsd.org>, freebsd-current <current@freebsd.org> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes Message-ID: <201812222009.wBMK9H5T050103@slippy.cwsent.com> In-Reply-To: Message from Yuri Pankov <yuripv@yuripv.net> of "Sat, 22 Dec 2018 21:03:26 %2B0300." <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri Pankov write s: > Yuri Pankov <yuripv@yuripv.net> wrote: >> In-Reply-To: <CAGGgMJf45vkNY6o6-in+kiAFHxsFZpKBc4Oa6qiCFnzKnRjk1g@mai l.gmail. >> com> >> Mark Peek wrote: >> > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper <yaneurabeya@gmail.com> wro= >> te: >> >=20 >> >> >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov <yuripv@yuripv.net> wrote: >> >>> >> >>> Mark Peek wrote: >> >>>> Thanks for the cc:. I forwarded the original report on to an interna= >> l >> >>>> VMware desktop product contact. >> >>> >> >>> Thank you. >> >>> >> >>>> What version of Workstation or Fusion is this occurring on? I saw >> >>>> Workstation 14 mentioned but curious if it occurs on Workstation 15 >> >>>> (latest). >> >>> >> >>> Running the latest available for download: 15.0.2 build-10952284. >> >> >> >> This is affecting me on VMware Fusion 11.0.1-11.0.2. I know it wasn=E2= >> =80=99t >> >> affecting me on 10.x. I didn=E2=80=99t install 11.0.0, so I don=E2=80=99= >> t know if it >> >> affects that version... >> >> >> >> Thanks so much! >> >> >> >> -Enji >> >=20 >> >=20 >> > BTW, there appears to be a workaround here using -o 'IPQoS=3Dthroughput= >> ' >> > (untested by me). I've seen the issue forwarded internally but no furth= >> er >> > discussions yet. >> >=20 >> > https://communities.vmware.com/thread/590825 > > Yes, that's exactly what the patch attached to original message does if > we are running as a VMware guest. The workaround is known and it works, > but it's not immediately clear and I just wanted it to be the default > for the time being. The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this intended? Juxtaposed to this, at $JOB where our VMware guests (mostly Linux and Windows) running on VMware clusters with NSX network (with plans to totally virtualize the network), we've noticed other network quirkiness, most notably with NFS between unlike O/S's, i.e. Solaris <--> Linux. I'm not surprised that this regression also exists. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201812222009.wBMK9H5T050103>