@larrikin
Hi, did you ever find a solution to this?

@enjoyit
Hi, I'm not using Gateway Group anymore. I've switched from OpenVPN to WireGuard.
My current anti-bufferbloat config is a combination of this two guides:
https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.html
https://isc.sans.edu/forums/diary/Securing+and+Optimizing+Networks+Using+pfSense+Traffic+Shaper+Limiters+to+Combat+Bufferbloat/27102/

@bartkowski
Noop.
Not using limiters right now.
"They" know the issue exists, something good will come out ... soon ...

@syserr-0, just use regular traffic shaping (e.g. fq codel) on the WAN interface of the office box?

Tutorial: https://forum.netgate.com/topic/112527/playing-with-fq_codel-in-2-4/814?_=1645275206163

@akuma1x many many thanks for your help :) I'm a newbie and users support its very useful in my case. I will take a look at th delinks you provided and I will try.

Just found another issue related to DSCP rules.
It seems that the rule will match TOS value instead of DSCP value.

For example, I originally set CS1 (DSCP value 8, equal to TOS value 32) in the rule, right now I need to set to CS4 instead to match the packet with DSCP value 8 (TOS value 32)

So I know now that it is not solved. It might not be dropping pings during speed tests but tracroute output still doesn't make sense.

So I'm going back to having fq_codel limiter on LAN in.

@sotirone I'd say if it's working then roll with it. :) Besides the traffic graph, Diagnostics/Limiter Info should show the relevant info. The router we have with limiters doesn't have floating rules, we have them on LAN to capture the outbound connections from certain IPs.

@steveits it worked. Thanks for the help.
Screenshot_20220211-190050.png

@serbus Hi John, since I cannot delete the limiter right now, I would try to "delete" it within the XML file. I will be on-site on Friday and give it a try...

Has anyone else any other suggestions?

I've partially discovered a solution more elegant than using Bash & SED to edit config.xml directly.

instead, I created files in /etc/phpshellsessions called 'throttleon' and 'throttleoff'. Contents:

require_once("config.inc"); require_once("filter.inc"); global $config; parse_config(true); $config['filter']['rule']['0']['disabled'] = false; write_config("throttleon");

throttleoff is exactly the same, but 'disabled' = true; instead.

I checked in the shell first to get the index of the rule i wanted to enable ( and it's rule '0', so that is why it's referenced in the code above ).

These can now be called via pfSsh.php playback throttleon ( or off ).

Interestingly, I tried to use the pfsense PHP shell record feature to do this, but it just created 0 byte files for some reason ( even though the commands in the session worked fine ).

It seems I don't need to call rc.filter_configure either, as playing back these files updates the rule enable/disable status ( maybe a feature of the shell? )