From owner-freebsd-bugs@freebsd.org  Thu May 25 18:59:43 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B1DED82836
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 25 May 2017 18:59:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AB2319E3
 for <freebsd-bugs@FreeBSD.org>; Thu, 25 May 2017 18:59:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4PIxgXP065191
 for <freebsd-bugs@FreeBSD.org>; Thu, 25 May 2017 18:59:43 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 219453] TCP MD5 broken for vlan interfaces created on lagg
Date: Thu, 25 May 2017 18:59:43 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: mav@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-219453-8-7y84PoG0bR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219453-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219453-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 May 2017 18:59:43 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219453

--- Comment #13 from Alexander Motin <mav@FreeBSD.org> ---
I see one problem with my change: when it tries to disable RXCSUM for em0,
since msk0 does not support it, em0 also disables TXCSUM, which lagg does n=
ot
notice.  But that should not affect vlan operation, since due to lack of
VLAN_HWCSUM on msk0 none of those flags propagated to vlan0 either before my
change or after.

I'd appreciate some comments here from people knowing how TCP MD5 is workin=
g.

Meanwhile, Marek, could you try to manually synchronize the msk0 and em0
interface capabilities (disable rxcsuma and txcsum) to see whether it change
anything.

--=20
You are receiving this mail because:
You are the assignee for the bug.=