<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Wizard sets default qLink Lower than qOthersLow]]></title><description><![CDATA[<p dir="auto">I'm brand new, so please be gentle…</p>
<p dir="auto">A couple weeks ago I replaced my dd-wrt box with pfSence. I'm on 2.3 and trying out traffic shaping. After running the wizard I noticed that on my LAN interface qLink (priority=2, queue limit=500) is the default queue. This seems strange to me since qOthersLow (priority=3, no limit) is a higher priority.</p>
<p dir="auto">I have a few questions...<br />
Did the wizard work correctly?<br />
If yes, then why is the default lower than low?<br />
What is the significance of the queue limit?<br />
Should I change the default, or just trust the wizard?</p>
<p dir="auto">Thanks<br />
Rich</p>
]]></description><link>https://forum.netgate.com/topic/99959/wizard-sets-default-qlink-lower-than-qotherslow</link><generator>RSS for Node</generator><lastBuildDate>Sun, 15 Mar 2026 20:56:17 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/99959.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 15 May 2016 18:05:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Wizard sets default qLink Lower than qOthersLow on Sun, 15 May 2016 22:22:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/pfuser0">@<bdi>pfuser0</bdi></a>:</p>
<blockquote>
<blockquote>
<p dir="auto">You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's own set of fundamental problems.</p>
</blockquote>
<p dir="auto">Thanks.<br />
I'm using PRIQ, but I don't remember actually choosing it over HFSC. I'll try switching.<br />
It still looks like qLink was being used for LAN&lt;–&gt;WAN traffic. In my setup the only LAN&lt;-&gt;LAN traffic hitting the router is management traffic (no DNS/DHCP).</p>
<p dir="auto">Anyone willing to share their insight into Queue Limit?</p>
</blockquote>
<p dir="auto">You are worrying about things that are currently not very useful to you. Here, read <a href="http://www.linksysinfo.org/index.php?threads/qos-tutorial.68795/" target="_blank" rel="noopener noreferrer nofollow ugc">this QoS tutorial</a>.</p>
<p dir="auto">The wizard is intended to be 1 setup that can work well everywherd, so everyone gets the qLink setup because it causes no harm to those who do not run multi-LAN.</p>
<p dir="auto">Queue limits make little difference. Most defaults are optimal. Search the forum for more info.</p>
]]></description><link>https://forum.netgate.com/post/624978</link><guid isPermaLink="true">https://forum.netgate.com/post/624978</guid><dc:creator><![CDATA[Nullity]]></dc:creator><pubDate>Sun, 15 May 2016 22:22:16 GMT</pubDate></item><item><title><![CDATA[Reply to Wizard sets default qLink Lower than qOthersLow on Sun, 15 May 2016 22:14:47 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto">You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's own set of fundamental problems.</p>
</blockquote>
<p dir="auto">Thanks.<br />
I'm using PRIQ, but I don't remember actually choosing it over HFSC. I'll try switching.<br />
It still looks like qLink was being used for LAN&lt;–&gt;WAN traffic. In my setup the only LAN&lt;-&gt;LAN traffic hitting the router is management traffic (no DNS/DHCP).</p>
<p dir="auto">Anyone willing to share their insight into Queue Limit?</p>
]]></description><link>https://forum.netgate.com/post/624976</link><guid isPermaLink="true">https://forum.netgate.com/post/624976</guid><dc:creator><![CDATA[pfuser0]]></dc:creator><pubDate>Sun, 15 May 2016 22:14:47 GMT</pubDate></item><item><title><![CDATA[Reply to Wizard sets default qLink Lower than qOthersLow on Sun, 15 May 2016 18:19:03 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/pfuser0">@<bdi>pfuser0</bdi></a>:</p>
<blockquote>
<p dir="auto">I'm brand new, so please be gentle…</p>
<p dir="auto">A couple weeks ago I replaced my dd-wrt box with pfSence. I'm on 2.3 and trying out traffic shaping. After running the wizard I noticed that on my LAN interface qLink (priority=2, queue limit=500) is the default queue. This seems strange to me since qOthersLow (priority=3, no limit) is a higher priority.</p>
<p dir="auto">I have a few questions...<br />
Did the wizard work correctly?<br />
If yes, then why is the default lower than low?<br />
What is the significance of the queue limit?<br />
Should I change the default, or just trust the wizard?</p>
<p dir="auto">Thanks<br />
Rich</p>
</blockquote>
<p dir="auto">The logic behind the default setup is kinda compex, especially for noobs. Hell, it confuses me too…</p>
<p dir="auto">1. A default queue should almost always be a low priority. You can't prioritize the bulk of your traffic... your connection can't magically send faster.</p>
<p dir="auto">2. The qLink is actually intended to be a work-around so that routed LAN-to-LAN traffic does not get traffic-shaped along with WAN traffic.</p>
<p dir="auto">You neglected to mention what algorithm you were using. HFSC does not even use the "Priority" parameter, and plain old Priority queueing has it's <a href="https://doc.pfsense.org/index.php/Traffic_Shaping_Guide#Priority_Queueing_.28PRIQ.29" target="_blank" rel="noopener noreferrer nofollow ugc">own set of fundamental problems</a>. (The exact priority is less important than who has the high priority <em>when there is congestion[/].)</em></p>
]]></description><link>https://forum.netgate.com/post/624949</link><guid isPermaLink="true">https://forum.netgate.com/post/624949</guid><dc:creator><![CDATA[Nullity]]></dc:creator><pubDate>Sun, 15 May 2016 18:19:03 GMT</pubDate></item></channel></rss>