Date: Tue, 25 Feb 2020 11:46:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 198406] More than 4 esxi vmxnet3 interfaces causes vlans attached to vmxnet interfaces to stop working Message-ID: <bug-198406-227-iqZzl7msTr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198406-227@https.bugs.freebsd.org/bugzilla/> References: <bug-198406-227@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=3D198406 --- Comment #12 from Tomek Lutelmowski <tomasz.lutelmowski@gmail.com> --- pfSense 2.4.4/2.4.5 under ESXi 6.7U3 here. I had similar issue which had driven me nuts. With 4 VMXNET3 cards, under h= igh load (~500mbit/s) pfSense was cutting off traffic on all VMXNET3s connected= to vSwitches with physical interfaces (traffic within virtual switch was fine). During downtime, tcpdump on interface doesn't show any incoming traffic). I tried changing VM driver to E1000, adjusting buffers, fiddle with MSI/inter= rupt settings, but no joy. Then I've tried pfsense 2.5.0 (devel, BSD 12) - and the problem is gone! No= w, what is really, really strange... I've created another VM machine (2.4.5 RC= ) in order to revert to more stable version. It was enough to boot up this machi= ne, without any configuration (but interfaces connected to VM switches), and the problem reappeared already on working machine (2.5.0) on the same ESXi! Wha= ts more - I had to reboot ESXi in order to fix it, as shutting down 2.4.5 was = not enough.=20 If you run pfSense under VMWare, look at gateway quality statistics for dro= ps, you may notice than under your VMXNET3 interface (connected to physical NIC= via vSwitch) may be dropping packets.=20 I hope this will help someone. Cheers, Tomek --=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-198406-227-iqZzl7msTr>