https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162011-06-02T04:32:52ZpfSense bugtrackerpfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=59452011-06-02T04:32:52ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Target version</strong> deleted (<del><i>2.0</i></del>)</li></ul> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=81912012-03-09T03:05:16ZNikolay Stoyanov
<ul></ul><p>I have same problem in latest 2.0.1-RELEASE.<br /><a class="external" href="http://forum.pfsense.org/index.php/topic,46469.0.html">http://forum.pfsense.org/index.php/topic,46469.0.html</a></p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=96662012-08-25T01:00:38ZBipin Chandrabipin@xbipin.com
<ul></ul><p>will this be fixed or is it fixed in 2.1?</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=100312012-11-27T01:44:40ZErmal Luçieri@pfsense.org
<ul></ul><p>Normally this can be overcommed with match rules on floating tab.<br />It is present there on 2.1 and i am pushing the fix to allow the rule for limiters as well.</p>
<p>Just create a Match rule under floating rules with limiters you want and it would be applied to these rules.</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=100322012-11-27T01:50:10ZErmal Luçieri@pfsense.org
<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>Applied in changeset <a class="changeset" title="Fixes #1575. Allow Match option to be used with limiters as well. The support is there in kernel ..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/84464c9ab0b94b9602c6ec62502dc4ad3e7a8c0a">84464c9ab0b94b9602c6ec62502dc4ad3e7a8c0a</a>.</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104222013-01-28T04:54:59ZBipin Chandrabipin@xbipin.com
<ul></ul><p>does seem to work still, upnp devices bypass limiter</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104312013-01-28T09:14:15ZErmal Luçieri@pfsense.org
<ul></ul><p>Can you provide any analysis of how you do your checking?<br />Also provide a <br /><pre>
ipfw pipe show
ipfw queue show
pfctl -vvsr
pfctl -vvsn
pfctl -a miniupnpd -vvsn
pfctl -a miniupnpd -vvsr
</pre></p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104352013-01-28T23:19:33ZBipin Chandrabipin@xbipin.com
<ul></ul><p>this was discussed here<br /><a class="external" href="http://forum.pfsense.org/index.php/topic,56092.0.html">http://forum.pfsense.org/index.php/topic,56092.0.html</a></p>
<p>the easy way to test this is, enable upnp, create limiters, create match rules under floating tab with limiters applied then u first do a speed test and it will be limited fine, now that same speed limit should apply but start a torrent download using utorrent or any such software and make it open a random port using upnp and then notice the download and upload speed exceed the limiter value and this way u know it never works once any application tries to open a port using upnp, the limiter almost becomes dead, it does work fine for other ports not opened by upnp</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104372013-01-29T03:35:25ZErmal Luçieri@pfsense.org
<ul></ul><p>In that forum post i do not see any limiters configured on the ruleset posted.<br />So please provide the information if you want this to be pursued.</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104392013-01-29T03:52:56ZBipin Chandrabipin@xbipin.com
<ul></ul><p>plz remove post after u have read it</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104452013-01-29T09:46:05ZErmal Luçieri@pfsense.org
<ul></ul><p>Can you try by removing the quick option on the match rules, if you have selected it?</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104462013-01-29T10:19:39ZBipin Chandrabipin@xbipin.com
<ul></ul><p>yes its ticked, trying without that now but if we untick then i guess in the past there was a problem of traffic for those clients not going to proper queues and i guess u only mentioned in the forum a very long time back that it needs to be ticked but for now i didnt assign any queues to those rules so no issues</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=104472013-01-29T10:30:12ZBipin Chandrabipin@xbipin.com
<ul></ul><p>tried it still same, clients upload speed exceeds limiter values</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=153472014-10-25T21:18:52ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Category</strong> set to <i>Traffic Shaper (Limiters)</i></li><li><strong>Affected Version</strong> changed from <i>2.0</i> to <i>All</i></li></ul> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=397402019-01-12T21:07:52ZAnonymous
<ul></ul><p>Is this issue still present in the latest development build?</p> pfSense - Bug #1575: Limiters are bypassed by local applications injecting ruleshttps://redmine.pfsense.org/issues/1575?journal_id=412102019-08-13T10:23:54ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>