[Bug 198406] More than 4 esxi vmxnet3 interfaces causes vlans attached to vmxnet interfaces to stop working

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406

--- Comment #12 from Tomek Lutelmowski <tomasz.lutelmowski at 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 high
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/interrupt
settings, but no joy.

Then I've tried pfsense 2.5.0 (devel, BSD 12) - and the problem is gone! Now,
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 machine,
without any configuration (but interfaces connected to VM switches), and the
problem reappeared already on working machine (2.5.0) on the same ESXi! Whats
more - I had to reboot ESXi in order to fix it, as shutting down 2.4.5 was not
enough. 

If you run pfSense under VMWare, look at gateway quality statistics for drops,
you may notice than under your VMXNET3 interface (connected to physical NIC via
vSwitch) may be dropping packets. 

I hope this will help someone.

Cheers,
Tomek

-- 
You are receiving this mail because:
You are the assignee for the bug.