pfSense

confirmed.
update: after reboot if the test limiter is applied as a pipe in the firewall rule the rule stops working - is unable to generate states
seems to be linked to limiter's bandwidth - 512Mb limiter works fine, 5 gig doesn't

Update:

Can confirm the above on 24.03

Logs shows:

Jan 9 13:11:27     php-fpm     56273     /rc.filter_configure_sync: The command '/sbin/dnctl /tmp/rules.limiter' returned exit code '65', the output was 'Line 34: bandwidth too large'

Lev Prokofev wrote in #note-2:

'Line 34: bandwidth too large'

The bandwidth on a limiter can't be over the maximum value of a 32-bit unsigned integer, which is ~4.3G. The GUI should probably prevent the value from being set that high.

                if (bw > UINT_MAX)
                        errx(EX_DATAERR, "bandwidth too large");

                *bandwidth = (uint32_t)bw;

But we need bandwidth limiter higher than ~4,3G. We need for example 7.5G or 10G
So changing just the UI is not very helpful.
Why not changing from a 32-bit unsigned integer to a 64-bit unsigned integer to allow higher values.
Or any other solution?

Running into a similar issue

https://forum.netgate.com/topic/196432/limiter-config-disappered/2

Albiet, my configurated limiter is set to 50Mbps but after a reboot the Limiter configuration is gone.

Thanks for the report. I've opened a separate issue here: https://redmine.pfsense.org/issues/16051

this also occurs in v25.03.b.20250306.0140 by setting a limiters value above 4.3gb