<?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[Limiter and QoS issue]]></title><description><![CDATA[<p dir="auto">For simplicity I created a qACK, qGame and qDefault queues to control the traffic. The priority order is qACK (the highest), qGame and qDefault. I defined floating rules and for game's ports I specified qACK/qGame queue. This worked like a charm, even when the link got saturated the gamers had no complain because the game's ping was low around 50ms. :-)</p>
<p dir="auto">Then I noticed that some users abuses the link and start to download a lot. The online games still worked fine but my ISP started to control the link speed after I reached some limit per month. Although the games still worked fine even after the lowered download speed I decided to introduce limits. I created tow limiters one for download one for upload e.g. 2Mbs download and 0.5Mbps upload. Modifier the default LAN static firewall rule and set the In/Out limiters. It again worked like a charm when I measured the allowed bandwidth for these users.</p>
<p dir="auto">However since I introduced the limiters the gamers started to complain that the ping is now around 150-300ms. Apparently pfSense ignores the QoS (queues) when it starts to limit the packets. Maybe I'm doing something wrong, any idea what? Or is this a known issue / limitation of limiters?</p>
<p dir="auto">I like the limiter idea because I can easily introduce several limiters and control the bandwith per IP + also control the QoS. I expected that the limiter will control the links speed while it will still obey the queue priority.</p>
<p dir="auto">Any idea how to correctly configure this?<br />
I'm on 2.1.3 NanoBSD (Alix board) version.</p>
<p dir="auto">Thanks, Peter</p>
]]></description><link>https://forum.netgate.com/topic/70275/limiter-and-qos-issue</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 02:24:18 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/70275.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 14 Jun 2014 12:40:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Limiter and QoS issue on Sun, 15 Jun 2014 18:51:00 GMT]]></title><description><![CDATA[<p dir="auto">They work fine together. I have previously documented that the limiter and QoS work fine together. I have shown screenshots of an LoL game going while downloading from Steam.</p>
<p dir="auto">LoL uses UDP not TCP for the game client once the game is started.  It uses port 80 during the setup of the game.</p>
<p dir="auto">Again if you can post screenshots of your setup so we can see it instead of blindly posting that it is not working then maybe we can help.</p>
<p dir="auto">Otherwise it appears you just want to troll.</p>
]]></description><link>https://forum.netgate.com/post/467459</link><guid isPermaLink="true">https://forum.netgate.com/post/467459</guid><dc:creator><![CDATA[sideout]]></dc:creator><pubDate>Sun, 15 Jun 2014 18:51:00 GMT</pubDate></item><item><title><![CDATA[Reply to Limiter and QoS issue on Sun, 15 Jun 2014 16:17:49 GMT]]></title><description><![CDATA[<p dir="auto">Today I decided to play the game what the gamers play - League of Legends. Indeed the ping was high ~300ms when the link was heavily pressured. What was interesting when I switched back to my previous OS (Gargoyle) the game reported ~50ms ping. I decided to grab the exact settings of the QoS, then switched back to pfSense.</p>
<p dir="auto">The difference was in the firewall floating rule which created a floating rule for UDP, port = 5000-5500, -/qGame, however on my previous OS the same port used TCP protocol NOT UDP. This rule was created by the pfSense traffic shaper wizard and it is apparently incorrect. Once I changed the rule to TCP and set qACK/qGame everything started to work like a charm :-)</p>
<p dir="auto">So I'm taking back my original assumption that QoS and limiter do not work together :-)</p>
]]></description><link>https://forum.netgate.com/post/467452</link><guid isPermaLink="true">https://forum.netgate.com/post/467452</guid><dc:creator><![CDATA[Peter.Hardwork]]></dc:creator><pubDate>Sun, 15 Jun 2014 16:17:49 GMT</pubDate></item><item><title><![CDATA[Reply to Limiter and QoS issue on Sat, 14 Jun 2014 15:04:37 GMT]]></title><description><![CDATA[<p dir="auto">You need to not modify the default LAN rule and make a new rule above it for the limter.  use IPv4 / TCP / any / any and then select the limiters.  The majority of gaming traffic is UDP so this will not affect it.  See this post - https://forum.pfsense.org/index.php?topic=63531.0 . This will define a limiter for ALL TCP connections that is shared by how many users there are and what bandwidth you define.  So if you define 20Mbits then if 4 people are trying to download , it will split the bandwidth among those 4 people.</p>
<p dir="auto">Additionally you can do some searching and find the ports need for Steam downloads and apply a QoS rule to them as well in the floating rules section.</p>
<p dir="auto">Hope this helps.</p>
]]></description><link>https://forum.netgate.com/post/467345</link><guid isPermaLink="true">https://forum.netgate.com/post/467345</guid><dc:creator><![CDATA[sideout]]></dc:creator><pubDate>Sat, 14 Jun 2014 15:04:37 GMT</pubDate></item></channel></rss>