Dag-Erling Smørgrav wrote:
> Yuri Pankov writes:
>> There's apparently a bug in VMware Workstation NAT implementation,
>> [...] The patch itself is attached.
>
> Could you please open a differential and add me as reviewer?
https://reviews.freebsd.org/D18636
And there's already a PR for this:
In message <865zvkpphn@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > I know our code is full of workarounds and theirs probably too. The
> > question is should we? IMO no.
>
> Unfortunately, the world is imperfect and does not care about your
>
Yuri Pankov writes:
> There's apparently a bug in VMware Workstation NAT implementation,
> [...] The patch itself is attached.
Could you please open a differential and add me as reviewer?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
Cy Schubert writes:
> Hmmm. I guess Red Hat Enterprise Linux must be a toy OS then.
I don't speak for them, but I assure you that both their code and ours
are full of workarounds for bugs in third-party software and hardware,
and it is ridiculous to claim otherwise.
> No. We do like Red Hat
Cy Schubert writes:
> I know our code is full of workarounds and theirs probably too. The
> question is should we? IMO no.
Unfortunately, the world is imperfect and does not care about your
opinion. 90% of the hardware we run on deviates from the spec in some
way or another and requires
In message <86pntszlae@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > Hmmm. I guess Red Hat Enterprise Linux must be a toy OS then.
>
> I don't speak for them, but I assure you that both their code and ours
> are full of workarounds for bugs in
Cy Schubert writes:
> Add it to ssh_config or sshd_config if one must but have VMware fix
> their bugs. Putting workarounds in our O/S to work around a bug in some
> other vendor's virtualization is something I don't support.
It's something we do *all the time*. Otherwise we'd just be a toy
In message <861s681ypd@next.des.no>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rg
rav?= w
rites:
> Cy Schubert writes:
> > Add it to ssh_config or sshd_config if one must but have VMware fix
> > their bugs. Putting workarounds in our O/S to work around a bug in some
> > other vendor's virtualization is
In message <82004750-097a-47e5-9981-86b4b7a5f...@gmail.com>, Enji
Cooper writes
:
> > On Dec 22, 2018, at 1:03 PM, Cy Schubert =
> wrote:
>
> =E2=80=A6
>
> > Regarding the Red Hat bugzilla bug, looks like they're doing the right
> > thing by reaching out to VMware. This should be our position as
> On Dec 22, 2018, at 1:03 PM, Cy Schubert wrote:
…
> Regarding the Red Hat bugzilla bug, looks like they're doing the right
> thing by reaching out to VMware. This should be our position as well.
> Add it to ssh_config or sshd_config if one must but have VMware fix
> their bugs. Putting
rotected-headers="v1"
> From: Yuri Pankov
> To: Cy Schubert
> Cc: Mark Peek , Enji Cooper ,
> Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?=
> , freebsd-current
> Message-ID: <0503b382-d886-39a4-d265-b43d8adc1...@yuripv.net>
> Subject: Re: workaround for VMw
protected-headers="v1"
>> From: Yuri Pankov
>> To: Cy Schubert
>> Cc: Mark Peek , Enji Cooper ,
>> Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?=
>> , freebsd-current
>> Message-ID:
>> Subject: Re: workaround for VMware WS NAT bug trigg
> To: Cy Schubert
> Cc: Mark Peek , Enji Cooper ,
> Warner Losh , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?=
> , freebsd-current
> Message-ID:
> Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1
> changes
> References: <20181009.wbmk9h5t050.
Cy Schubert wrote:
> In message <913730b6-c6f0-60b8-a589-e89e872b7...@yuripv.net>, Yuri
> Pankov write
> s:
>> Yuri Pankov wrote:
>>> In-Reply-To: l.gmail.
>>> com>
>>> Mark Peek wrote:
On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper
> wro=
>>> te:
=20
>
>> On Dec 21, 2018, at
In message <913730b6-c6f0-60b8-a589-e89e872b7...@yuripv.net>, Yuri
Pankov write
s:
> Yuri Pankov wrote:
>> In-Reply-To: > com>
>> Mark Peek wrote:
>> > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper
wro=
>> te:
>> >=20
>> >>
>> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote:
>> >>>
>> >>> Mark
On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov Mark Peek wrote:
> > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper
> wrote:
> >
> >>
> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote:
> >>>
> >>> Mark Peek wrote:
> Thanks for the cc:. I forwarded the original report on to an internal
>
Mark Peek wrote:
> On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote:
>
>>
>>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote:
>>>
>>> Mark Peek wrote:
Thanks for the cc:. I forwarded the original report on to an internal
VMware desktop product contact.
>>>
>>> Thank you.
>>>
What
On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote:
>
> > On Dec 21, 2018, at 17:48, Yuri Pankov wrote:
> >
> > Mark Peek wrote:
> >> Thanks for the cc:. I forwarded the original report on to an internal
> >> VMware desktop product contact.
> >
> > Thank you.
> >
> >> What version of Workstation
> On Dec 21, 2018, at 17:48, Yuri Pankov wrote:
>
> Mark Peek wrote:
>> Thanks for the cc:. I forwarded the original report on to an internal
>> VMware desktop product contact.
>
> Thank you.
>
>> What version of Workstation or Fusion is this occurring on? I saw
>> Workstation 14 mentioned
Mark Peek wrote:
> Thanks for the cc:. I forwarded the original report on to an internal
> 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
Thanks for the cc:. I forwarded the original report on to an internal
VMware desktop product contact.
What version of Workstation or Fusion is this occurring on? I saw
Workstation 14 mentioned but curious if it occurs on Workstation 15
(latest).
Mark
On Fri, Dec 21, 2018 at 4:19 PM Warner Losh
I've been hit by this as well. At least two others on IRC have had the same
issue.
Warner
On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote:
>
> > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote:
> >
> > Hi,
> >
> > There's apparently a bug in VMware Workstation NAT implementation, made
> >
> On Dec 21, 2018, at 3:55 PM, Yuri Pankov 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
23 matches
Mail list logo
