Date: Mon, 17 Sep 2018 06:18:58 +0200 From: Kurt Jaeger <pi@freebsd.org> To: Kristof Provost <kp@freebsd.org> Cc: Eric van Gyzen <eric@vangyzen.net>, Kurt Jaeger <pi@freebsd.org>, freebsd-current@freebsd.org, freebsd-net@freebsd.org Subject: Re: Bad DHCP Checksums over VLANs Message-ID: <20180917041858.GH2118@home.opsec.eu> In-Reply-To: <2D1D4467-2256-40C5-B69F-B9BDC7C7F7D6@FreeBSD.org> References: <9dd3c7f9-d970-5d30-ebf2-c0f40c76011b@vangyzen.net> <20180915060615.GF2118@home.opsec.eu> <794ae64b-54d8-cfde-2e9c-87b3b74e0516@vangyzen.net> <2D1D4467-2256-40C5-B69F-B9BDC7C7F7D6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > >> 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. > > > I had a similar issue, where -vlanhwtag also fixed it. > That was on a I210 (gib) card (in a FreeNAS mini XL). I've created a PR for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231416 -- pi@FreeBSD.org +49 171 3101372 2 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180917041858.GH2118>