Limiters are bypassed by local applications injecting rules
Taking a look at http://forum.pfsense.org/index.php/topic,37399.0.html
it would be good to teach the match action about limiters as well to avoid such kind of issues.
#2 Updated by Nikolay Stoyanov about 7 years ago
I have same problem in latest 2.0.1-RELEASE.
#4 Updated by Ermal Luçi over 6 years ago
Normally this can be overcommed with match rules on floating tab.
It is present there on 2.1 and i am pushing the fix to allow the rule for limiters as well.
Just create a Match rule under floating rules with limiters you want and it would be applied to these rules.
#8 Updated by Bipin Chandra over 6 years ago
this was discussed here
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
#12 Updated by Bipin Chandra over 6 years ago
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