Bug #9643

Limiters do not function properly on 2.5 snapshots

Added by Greg M about 2 months ago. Updated 22 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


Hi all!

Discussion here:

I think there is a bug in limiters...

Problem #1:
When I create limiters and set floating firewall rules for WAN interface, all traffic from all LANs stops working. If I create floating rules
with same limiters for LAN interfaces, everything works.
I was following forum discussion samples and tutorials, YouTube videos etc... Limiters were set up properly and floating rules as well.

Problem #2:
With limiter on LAN ifaces all traffic on LAN iface is limited to 80 Mbit/s which is OK.
But when I start to download torrent for example, LAN stays at 80 Mbit/s but WAN goes above 80 and eventually reaches 90 Mbit/s.
There is no other sources of traffic just torrents. One WAN and 2 LAN.
See image:

Because of problem #2, I was trying to limit WAN iface instead of LAN to avoid this issue but when I did that, it blocked all traffic completely.

Pfsense is on Hyper-V.

Using latest snapshot as of today.

We can continue on forums to avoid spamming here, but I think something is not quite right with limiters on 2.5.0 snaps.



#1 Updated by Greg M about 2 months ago

Hi again.

I restored config on 2.4.4-p3 and this are working just fine there.

I believe this on is related to .


#2 Updated by Jim Pingle about 2 months ago

  • Category set to Limiters
  • Target version set to 2.5.0

The two cannot be related. ALTQ is not used for limiters.

I have also seen a similar situation on 2.5 where limiters were not functional and had to be removed to pass traffic.

#3 Updated by Greg M about 2 months ago

Hmmm OK, I have Hyper-V, 2.5.0 and pppoe.

But weird is, that on when applied on IN direction on LAN it works ok.

#4 Updated by Jim Pingle 27 days ago

  • Subject changed from Limiters in 2.5 to Limiters do not function properly on 2.5 snapshots

#5 Updated by Grant Peier 22 days ago

I experienced the same behavior as Greg M when updating from 2.4.4-p3 to 2.5.0. This was on a bare-metal install.

Also available in: Atom PDF