Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Dec 2018 23:13:49 +0300
From:      Yuri Pankov <yuripv@yuripv.net>
To:        Cy Schubert <Cy.Schubert@cschubert.com>
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:  <e84b7b4a-89ab-2ad9-ac3a-e08b8491e5cc@yuripv.net>
In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com>
References:  <201812222009.wBMK9H5T050103@slippy.cwsent.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH
Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi";
 protected-headers="v1"
From: Yuri Pankov <yuripv@yuripv.net>
To: Cy Schubert <Cy.Schubert@cschubert.com>
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>
Message-ID: <e84b7b4a-89ab-2ad9-ac3a-e08b8491e5cc@yuripv.net>
Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1
 changes
References: <201812222009.wBMK9H5T050103@slippy.cwsent.com>
In-Reply-To: <201812222009.wBMK9H5T050103@slippy.cwsent.com>

--c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Cy Schubert wrote:
> In message <913730b6-c6f0-60b8-a589-e89e872b7f42@yuripv.net>, Yuri=20
> 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=3D
>>> te:
>>>> =3D20
>>>>>
>>>>>> 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=20
> interna=3D
>>> l
>>>>>>> VMware desktop product contact.
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>>> What version of Workstation or Fusion is this occurring on? I=20
> saw
>>>>>>> Workstation 14 mentioned but curious if it occurs on=20
> 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=20
> wasn=3DE2=3D
>>> =3D80=3D99t
>>>>> affecting me on 10.x. I didn=3DE2=3D80=3D99t install 11.0.0, so I=20
> don=3DE2=3D80=3D99=3D
>>> t know if it
>>>>> affects that version...
>>>>>
>>>>> Thanks so much!
>>>>>
>>>>> -Enji
>>>> =3D20
>>>> =3D20
>>>> BTW, there appears to be a workaround here using -o=20
> 'IPQoS=3D3Dthroughput=3D
>>> '
>>>> (untested by me). I've seen the issue forwarded internally but no=20
> furth=3D
>>> er
>>>> discussions yet.
>>>> =3D20
>>>> https://communities.vmware.com/thread/590825
>>
>> Yes, that's exactly what the patch attached to original message does i=
f
>> we are running as a VMware guest.  The workaround is known and it work=
s,
>> but it's not immediately clear and I just wanted it to be the default
>> for the time being.
>=20
> The patch assumes VMWARE_GUEST_WORKAROUND unconditionally. Is this=20
> intended?

It's the added code that is ifdef'ed VMWARE_GUEST_WORKAROUND, so it can
be ripped out easily when no longer needed, and yes, it's enabled
unconditionally for now.  And the check itself is if 'kern.vm_guest'
reports 'vmware'.

> Juxtaposed to this, at $JOB where our VMware guests (mostly Linux and=20
> Windows) running on VMware clusters with NSX network (with plans to=20
> totally virtualize the network), we've noticed other network=20
> quirkiness, most notably with NFS between unlike O/S's, i.e. Solaris=20
> <--> Linux. I'm not surprised that this regression also exists.
>=20
>=20



--c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi--

--NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlwemv0ACgkQk4vgf7Eq
4WzRYQgAkYY2fb3KicgVMkTSVjP+g3mEz0xqAQIVnOKaRDfXOqAG3sgSqp5FkEiz
OqQYlFfgeg6hOIIKUpsJc0DU7TTZUNtVw1XNihb3JlHIufe3XU2p6zER2jBqPObW
xAltGgZfd3cKeR+bKV2jKTEFmuUjRyTu8X1heWK0RZ09Wa+mBeEgcoSOJJDuEHRY
vs5QeqduyhoxN7GAIlkgsUCCEDzeoAW4x+6OqYC3QFgw/VwD8EUJpMD2A1s8OUTw
GrFYvuWiH0k/YbIQyhY04vUIVNR4VqQFrL7d+eiIAhA5Q0vpDrf8KDgev+NDYRiY
cOg0wABTh/vkYW+B3p4Ef5jL3HrT/Q==
=l+NN
-----END PGP SIGNATURE-----

--NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e84b7b4a-89ab-2ad9-ac3a-e08b8491e5cc>