AltQ on HN(4) disable
-
I've asked this question in the past but never really received a satisfactory answer, partially because of being a novice, partially because there isn't a clear explanation in the docs.
I'm running a bare metal pfsense box. It is comprised of the following hardware:
i5-7500
32Gigs of ram (yeah, more than enough, but it came with it, so..)
intel i350-t2v2.Correct me if i'm wrong: hn nic stands for "hyper v", correct?
so, on a bare metal system like mine, the "multi Queue API" is activated by default because there's no hn nic? so, if i were to disable (uncheck) that box, it theoretically wouldn't make a difference?Is this where i can go and add some limiters with FQ_CoDel and improve my latency? or do i need to have the AltQ API enabled to use FQ_CoDel? from what i've read it seems that AltQ is antiquated compared to the multi Queue API and that I should disable this, and apply limiters to the multi queue api..
the description is pretty unclear. If i understood it i'd rewrite it and submit it as a fix for documentation so other novices like myself are able to follow..
Thanks for you time!
-
Yes, that setting makes no difference if you don't have any hn(4) NICs. And yes they are found in Hyper-V (and Azure).
The 'the multi Queue API' here applies only to hn NICs. You sacrificed mutiqueue to enable AltQ there but not on any other NIC.
You can apply FQ_CoDel using Limiters, yes.
https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.htmlSteve
