From owner-freebsd-current@freebsd.org Sat Dec 22 17:50:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A91061359A95 for ; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4056C6A88F for ; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 03D321359A94; Sat, 22 Dec 2018 17:50:58 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D56351359A93 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D7FC6A886 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mp) by smtp.freebsd.org (Postfix) with ESMTPSA id 408231522 for ; Sat, 22 Dec 2018 17:50:57 +0000 (UTC) (envelope-from mp@freebsd.org) Received: by mail-yb1-f176.google.com with SMTP id t16so1701214ybk.10 for ; Sat, 22 Dec 2018 09:50:57 -0800 (PST) X-Gm-Message-State: AA+aEWbC0AsREXBcn9lAJgGFMm23j+8mDeD45hJYI0huZShTOCQSVwrr Nfi8tzL5gRwa3IeMaiwGNRx7xKokpM7r2pRFVT5uGA== X-Google-Smtp-Source: AFSGD/Ub3hRLJslif0XzgUbVRR9xTvsyrtCggKid6VsWsLIW6OO4I+U0x3HghOKbaR7f+NoPz/Zj5NCuF5AwVVutvYk= X-Received: by 2002:a25:4b02:: with SMTP id y2mr7046342yba.387.1545501056748; Sat, 22 Dec 2018 09:50:56 -0800 (PST) MIME-Version: 1.0 References: <7c62852d-8be2-e351-99ba-d9e85f4c8a71@yuripv.net> <6c18cc85-0240-034d-01dd-84c20521c238@yuripv.net> <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> In-Reply-To: <980AA7F3-A447-45DC-A538-8EA89515F7DF@gmail.com> From: Mark Peek Date: Sat, 22 Dec 2018 09:50:45 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes To: Enji Cooper Cc: Yuri Pankov , Mark Peek , Warner Losh , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-current X-Rspamd-Queue-Id: 7D7FC6A886 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2018 17:50:59 -0000 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 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 further discussions yet. https://communities.vmware.com/thread/590825 Mark