Bufferbloat - Traffic Limiter not working in ESXI
-
Hi. I have been running pfsense for years, both on metal and in esxi. When running on metal, I use bufferbloat exactly as described by Lawrence in this video: https://www.youtube.com/watch?v=iXqExAALzR8 and it works perfectly. No issues. When running on exactly the same machine but this time in a VM on ESXI, the rule does not work and I also repeatedly get this error message: config_aqm Unable to configure flowset, flowset busy!
I see I am not the only one that this impacts from this thread https://www.reddit.com/r/PFSENSE/comments/9j1h8u/244_codel_limiter_error/ (although some suggest the error message is just SPAM and the rule works - I have found for me not to be the case. The rule does not work).
I have tried under ESXI 7 running pfsense in a ESXI VM 6.7 (on ESXI 7) using passthrough NIC's (intel) so not relying on VMware to do the networking. I have also tried not doing passthrough and using the VMware networking. I get the same result. Failure.
Back on metal, it works fine.
My internet speeds are 1000mbps / 400mbps
The reason bufferbloat is so important in Australia is our National Broadband Network (the only network that provides broadband) severely throttles if you get close to the 400mbps, which results in the upload dropping to 250mbps, and massive packet loss. The way around it is to limit exactly as described in the video to 380mbps and no packet loss, and you avoid hitting the National Broadband Network policer. Hopefully all that makes sense.
So back to my question - is this bufferbloat error specifically within ESXI a problem that people are aware of (again, its not the SPAM that's the issue - I do get the SPAM on my console - its the fact that it no longer works in ESXI)? I am also running the latest pfsense 2.5.1
-
@larrikin
Hi, did you ever find a solution to this?