Date: Sun, 26 Jul 2020 18:16:07 -0400 From: Joe Clarke <jclarke@marcuscom.com> To: freebsd-stable@freebsd.org Subject: Traffic "corruption" in 12-stable Message-ID: <9FAE54DE-F409-4A53-B91E-59AE52A86513@marcuscom.com>
next in thread | raw e-mail | index | archive | help
About two weeks ago, I upgraded from the latest 11-stable to the latest = 12-stable. After that, I periodically see the network throughput come = to a near standstill. This FreeBSD machine is an ESXi VM with two = interfaces. It acts as a router. It uses vmxnet3 interfaces for both = LAN and WAN. It runs ipfw with in-kernel NAT. The LAN side uses a = bridge with vmx0 and a tap0 L2 VPN interface. My LAN side uses an MTU = of 9000, and my vmx1 (WAN side) uses the default 1500. Besides seeing massive packet loss and huge latency (~ 200 ms for on-LAN = ping times), I know the problem has occurred because my lldpd reports: Jul 26 15:47:03 namale lldpd[1126]: frame too short for tlv received on = bridge0 And if I turn on ipfw verbose messages, I see tons of: Jul 26 16:02:23 namale kernel: ipfw: pullup failed This leads to me to believe packets are being corrupted on ingress. = I=E2=80=99ve applied all the recent iflib changes, but the problem = persists. What causes it, I don=E2=80=99t know. The only thing that changed (and yes, it=E2=80=99s a big one) is I = upgraded to 12-stable. Meaning, the rest of the network infra and = topology has remained the same. This did not happen at all in = 11-stable. I=E2=80=99m open to suggestions. Thanks. Joe --- PGP Key : http://www.marcuscom.com/pgp.asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9FAE54DE-F409-4A53-B91E-59AE52A86513>