Traffic Shaper: Limiter
-
Firewall: Traffic Shaper: Limiter
I rebuilt our firewall because the new pfSense broke our traffic shaping rules.
After export/import ruleset I still can't get traffic shaping to work on firewall WAN rules.
It seems to work fine on outgoing LAN rules though.Any ideas why it stopped working on WAN side?
This setup used to work before on incoming traffic, now it breaks the rule if I do this.
-
https://redmine.pfsense.org/issues/4326
-
Looks like the same problem.
Only we don't run Squid (with or without transparent mode.) -
I could not wait any longer.
I ended up downloading older version with working bandwidth limiter and installed that.
So far 16 hours of wasted time. -
Recent upgrade broke my traffic shaping too :(
What older version did you roll back to? -
I'm still running 2.1.5 on all our FW's.
Just testing the new 2.2.2 to see if the problem has been fixed in it. So much work over this. It's truly annoying.Sam
-
Not fixed yet. https://redmine.pfsense.org/issues/4326
Updated by Chris Buechler about 1 month ago
Target version changed from 2.2.1 to 2.2.2 -
Not fixed yet. https://redmine.pfsense.org/issues/4326
Updated by Chris Buechler about 1 month ago
Target version changed from 2.2.2 to 2.2.3 -
Not fixed yet.
Seems like some1 does not want this fixed.
Target version changed from 2.2.3 to 2.3 -
I too am having an issue with Limiters and LAGG groups. In 2.2.2 it didn't work at all for WAN. In 2.2.3, if you don't set an out limiter, it seems to work.
I had to change over from Shaper to Limiter as I moved to LAGG. I had to move to LAGG because CARP state sync change from pseudo interface (WAN/LAN) to actual interface name (igp0/igp1).
How is 2.2.4 looking in regards to LAGG with Limiters? I will take LAGG and ALTq as well. or hang it all and go back to allowing different interface for clustering. (Using WAN/LAN).Thanks for the great product. We have loved using it and love to see how it goes from here.
-
This is a great product. Wished they fixed this issue since these features is mostly used together in production environment.
-
Yes, agreed. Does not look like its fixed in 2.2.4. :(
-
There is not even a target version posted on Redmine anymore.
I wonder if we have to stay with 2.1.5 forever? -
Is only 6 months old bug, whats the rush… it needed > 2 years to fix Schedule States bug and this new one appeared in exchange. :'(
-
This Limiter thing on 2.2 is a real downer. It's beginning to feel like they don't know how to fix it.
-
Still nothing about Bug #4326
https://doc.pfsense.org/index.php/2.2.5_New_Features_and_Changes
-
It's currently listed under 2.3
https://redmine.pfsense.org/issues/4326
-
Wanted to inquire to see if anyone had additional info on this.
https://redmine.pfsense.org/issues/4326
-
No, it's still broken obviously as you can see from the bug status.
-
Yeah - I had that, which is why I asked if anyone had ADDITIONAL info, and not "is it fixed yet?" But thanks for playing.
