https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-01-02T09:49:29ZpfSense bugtrackerpfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=302732017-01-02T09:49:29ZJim Pingle
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/30273/diff?detail_id=23602">diff</a>)</li></ul> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=302822017-01-02T13:09:59ZLandon Timothytimotl@gmail.com
<ul></ul><p>For what it's worth, I saw the same behavior with igb interfaces after restoring a 2.3 config with a shaper.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=303102017-01-03T17:14:13ZGreg Siemon
<ul></ul><p>This appears to be caused by r263259 in FreeBSD 11 - Add Tx/Rx multiqueue support to vmx(4).</p>
<p>I believe that ALTQ does not support multiqueues and needs to be complied with the flag VMXNET3_LEGACY_TX flag enabled in order to get it working with ALTQ working again. See Forums posts details relating to ALTQ and IGB when multiqueue was enabled on that driver:</p>
<p><a class="external" href="https://forum.pfsense.org/index.php?topic=122367.0">https://forum.pfsense.org/index.php?topic=122367.0</a></p>
<p>From the revised Makefile in FreeBSD 11 (<a class="external" href="https://svnweb.freebsd.org/base?view=revision&revision=263259">https://svnweb.freebsd.org/base?view=revision&revision=263259</a>):</p>
<pre>
# With VMXNET3_LEGACY_TX, the driver will use the non-multiqueue
35 # capable if_start interface.
36 #CFLAGS+= -DVMXNET3_LEGACY_TX
</pre> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=303132017-01-03T21:23:44ZMichael OBrien
<ul></ul><p>I also see this on Hyper-V virtual NICs (not legacy). Perhaps this is a more generalized issue?</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304342017-01-07T12:13:43ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul><p>Personally, I think ALTQ is dead.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304532017-01-07T22:18:11ZChris Collins
<ul></ul><p>Jim ALTQ does looks its on the a downward path but still pfSense uses it and the traffic shaper is an established key feature.</p>
<p>Looking at FreeBSD problem tickets is confusing, I find some saying igb needs patching, but I also found one where apparently a patch was commited to auto enable legacy queuing when ALTQ is compiled into kernel.</p>
<p><a class="external" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409</a></p>
<p>Also to confirm igb is broken on pfSense 2.4 and ALTQ</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304582017-01-08T09:18:39ZJim Thompsonjim@netgate.com
<ul></ul><p>Chris Collins wrote:</p>
<blockquote>
<p>Jim ALTQ does looks its on the a downward path but still pfSense uses it and the traffic shaper is an established key feature.</p>
<p>Looking at FreeBSD problem tickets is confusing, I find some saying igb needs patching, but I also found one where apparently a patch was commited to auto enable legacy queuing when ALTQ is compiled into kernel.</p>
<p><a class="external" href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409</a></p>
<p>Also to confirm igb is broken on pfSense 2.4 and ALTQ</p>
</blockquote>
<p>ALTQ may be broken, but igb is likely fine.</p>
<p>That "patch" is a bodge, and I am unlikely to being in "legacy tx" support to pfsense.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304632017-01-08T10:36:22ZJim Pingle
<ul></ul><p>If there is any issue with igb, I can't replicate it here. On an SG-8860 with igb running 2.4, I can use ALTQ and it has multiple queues on the NICs.</p>
<p>The only type of NICs that fail in this way that I have tried so far are the vmx(4) interfaces from the original report.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304782017-01-08T19:13:37ZGreg Siemon
<ul></ul><p>Jim Pingle wrote:</p>
<blockquote>
<p>If there is any issue with igb, I can't replicate it here. On an SG-8860 with igb running 2.4, I can use ALTQ and it has multiple queues on the NICs.</p>
<p>The only type of NICs that fail in this way that I have tried so far are the vmx(4) interfaces from the original report.</p>
</blockquote>
<p>I swapped the VM interfaces from VMXNET3 to EM1000 and no sign of the error anymore. There does appear to be a cosmetic bug in the Traffic Shaper interface which states "This firewall does not have any interfaces assigned that are capable of using ALTQ traffic shaping." Traffic is being assigned to queues and there are no errors in the system logs. Can't seem to see the bug report the OP refers to here (seeing the same with igb interfaces: <a class="external" href="https://forum.pfsense.org/index.php?topic=123639.0">https://forum.pfsense.org/index.php?topic=123639.0</a></p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304792017-01-08T19:50:49ZJim Pingle
<ul></ul><p>What page does the error show on, exactly? I can't replicate any problem where that error shows up on a firewall that is actually capable of using the shaper.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=304802017-01-08T20:02:21ZGreg Siemon
<ul></ul><p>Firewall-Traffic Shaper-By Interface. I didn't check the others. If I see traffic in the queues then AltQ should be working right?</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=305052017-01-09T12:35:57ZJim Pingle
<ul><li><strong>Assignee</strong> changed from <i>Jim Pingle</i> to <i>Luiz Souza</i></li></ul><p>OK I put that back on <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: This firewall does not have any interfaces assigned that are capable of using ALTQ traffic shapin... (Resolved)" href="https://redmine.pfsense.org/issues/7102">#7102</a>, it's all unrelated to this ticket. This ticket is now (again) only for vmx(4) lacking ALTQ support. No other interface types are affected that I've found.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=309802017-01-30T00:30:55ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Should work now: <a class="external" href="https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb">https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb</a></p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=309982017-01-30T15:54:28ZGreg Siemon
<ul></ul><p>Luiz Otavio O Souza wrote:</p>
<blockquote>
<p>Should work now: <a class="external" href="https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb">https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb</a></p>
</blockquote>
<p>Thanks. Will test as soon as the snapshots update (still on 29 Jan at the moment).</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=310212017-01-31T18:57:56ZGreg Siemon
<ul></ul><p>Luiz Otavio O Souza wrote:</p>
<blockquote>
<p>Should work now: <a class="external" href="https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb">https://github.com/pfsense/FreeBSD-src/commit/91384809a74dc98ef0d2a173718bd79bd77c13bb</a></p>
</blockquote>
<p>Confirmed fixed here. No errors reported using ALTQ and 6 x VMXNET3 interfaces on ESXi 6.5.</p> pfSense - Bug #7066: vmx(4) interfaces do not have ALTQ support on pfSense 2.4, they had ALTQ support on 2.3https://redmine.pfsense.org/issues/7066?journal_id=310332017-02-01T09:47:29ZLuiz Souzaluiz@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Thanks!</p>