From owner-freebsd-current@freebsd.org Sun Sep 16 21:05:44 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 13F8C10AAE83; Sun, 16 Sep 2018 21:05:44 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (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 B4DF880D61; Sun, 16 Sep 2018 21:05:43 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from hammy.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 87A6D5646F; Sun, 16 Sep 2018 16:05:42 -0500 (CDT) Subject: Re: Bad DHCP Checksums over VLANs To: Kurt Jaeger Cc: freebsd-current@freebsd.org, freebsd-net@freebsd.org References: <9dd3c7f9-d970-5d30-ebf2-c0f40c76011b@vangyzen.net> <20180915060615.GF2118@home.opsec.eu> From: Eric van Gyzen Message-ID: <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> Date: Sun, 16 Sep 2018 16:05:41 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180915060615.GF2118@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Sun, 16 Sep 2018 21:05:44 -0000 On 9/15/18 1:06 AM, Kurt Jaeger wrote: > Can you disable all the options of the NIC ? > > ifconfig igb0 -rxcsum -txcsum -wol -tso4 -vlanmtu -vlanhwtag -vlanhwcsum -vlanhwtso > > Try to disable everything that can be disabled, e.g. LRO etc. Disabling vlanhwtag works around the problem. Also note that only DHCP traffic has this problem. If I assign an address manually, all traffic flows normally. Maybe the problem is in the BPF send path. Eric