Date: Wed, 26 Oct 2022 13:34:08 +0200 From: Franco Fichtner <franco@opnsense.org> To: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: netstat -I ix0 Message-ID: <65A102E0-D0A8-470B-8FAB-6B4957E239A7@opnsense.org> In-Reply-To: <CAKeEC-LTACAi4S_rT%2Bxw4Rf--jnMmp9cCqusFXSMDq15FLLwsA@mail.gmail.com> References: <3095c007-2582-32f2-c203-db0a30af14a8@otcnet.ru> <2afa3987d7f35bb655f9eb63aa6f4451@korbank.pl> <CAKeEC-KWLoiczDFvUPp0PJLev%2BqT6iwoWbE0bZVZS6U7SDq8JA@mail.gmail.com> <7d62ceba-3878-3ec7-9b9e-844d56641514@otcnet.ru> <CAKeEC-LTACAi4S_rT%2Bxw4Rf--jnMmp9cCqusFXSMDq15FLLwsA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 26. Oct 2022, at 13:11, Cristian Cardoso = <cristian.cardoso11@gmail.com> wrote: >=20 > Despite the error increments in the interface, I used the equipment = for a month until I migrated my things from the router I had and even = with a large error increment I didn't have any problems with packet loss = or routing. The cards exhibiting this input error are counting (valid) zero-checksum UDP packets as input errors despite handling them just fine. This is a documented errata. I think the whole "problem" started when Intel opted to push all interface errors into the input error counter in FreeBSD 13 which surfaced this non-issue. Cheers, Franco=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?65A102E0-D0A8-470B-8FAB-6B4957E239A7>