pfSense plus 24.11
-
@stephenw10 I tried a lot of way and not working with official guide and non official. In traffic shaping topic a lot of guys wrote about this.
-
I use Limiters all the time and they're working fine. What exactly are you seeing? How does it fail?
-
@stephenw10 When check bufferbloat on waveform I don't see any difference really.
-
@stephenw10 Limiters should work fine, when use OpenVPN regarding pfSense doc but in reality nothing
-
So you are specifically trying to address buffer bloat? Or just limiting traffic?
-
@stephenw10 Actually for me important bufferbloat and tried to set tail drop with fgcodel and always nothing to work. Limiters graph working show something but nothing improving in real. Somewehere on other forum i saw a tip to clean xml config format from reaming's of limiters settings but don't know how to do this. Because was wrote that sometimes when delete limiters something remani9ng and don't remove, so next time old settings and new are mixing
-
Ok so you are not seeing a general problem with Limiters not working at all?
Just when used to address buffer bloat with CoDel?
As shown here: https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.html
So when you tried it what happened? It just didn't help with buffer bloat? It didn't pass traffic at all? Some other error?
-
-
Hmm, did you see any difference at all?
It could be that your connection is sufficiently bad that it can't help much. Or needs tuning for the conditions.
-
@stephenw10
To be honest, tested official guide for buffrebloat and this is guide: https://isc.sans.edu/diary/Securing+and+Optimizing+Networks+Using+pfSense+Traffic+Shaper+Limiters+to+Combat+Bufferbloat/27102/First official never work, second work very well but only with clean installation of pfSense without any my firewall rules and VPN settings. After any changes in firewall and etc even second guide stop working!
-
Then it sounds like you are adding rules that accidentally bypass the Limiters.
Nothing has changed in 24.11 in that regard. But this seems more like a config error than a bug in Limiters.
