Date: Thu, 25 May 2017 18:59:43 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219453] TCP MD5 broken for vlan interfaces created on lagg 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219453-8-7y84PoG0bR>