Date: Sat, 22 Dec 2018 11:16:39 -0700 From: Warner Losh <imp@bsdimp.com> To: Yuri Pankov <yuripv@yuripv.net> Cc: Mark Peek <mp@freebsd.org>, Garrett Cooper <yaneurabeya@gmail.com>, =?UTF-8?Q?Dag=2DErling_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: <CANCZdfqNpXcsgn3y2wAuLfk4U-JeXGyeYu__TrFJMjQH%2BwAXvg@mail.gmail.com> In-Reply-To: <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net> References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <B4FC7B2E-780C-4F9F-BFA3-3B9D05259D56@gmail.com> <CANCZdfrabc%2BVT=L=KE1ScfmOuebzb7hoVDqzGLr4Q1DANhEaaA@mail.gmail.com> <CAGGgMJcF1RUS0%2Bz3FNM8WbyMx2-oDrVu2CKZusQ3mxqCCdtH5w@mail.gmail.com> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> <CAGGgMJf45vkNY6o6-in%2BkiAFHxsFZpKBc4Oa6qiCFnzKnRjk1g@mail.gmail.com> <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov <yuripv@yuripv.net wrote: > Mark Peek wrote: > > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper <yaneurabeya@gmail.com> > wrote: > > > >> > >>> 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= =99t know if it > >> affects that version... > >> > >> Thanks so much! > >> > >> -Enji > > > > > > 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. > > > > 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. > Fixes my world... Warner >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqNpXcsgn3y2wAuLfk4U-JeXGyeYu__TrFJMjQH%2BwAXvg>