Project

General

Profile

Actions

Bug #16037

open

New CoDel limiters are no longer created with any default values

Added by Andrew Almond 2 months ago. Updated about 2 months ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper (Limiters)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.11
Affected Architecture:
All

Description

When creating new limiters as per the documentation, the parameters are no longer set to default values as was done in previous versions of pfSense. target and interval are both 0 , and quantum , limit , and flows are blank. The text boxes are empty and don't contain any greyed-out text, indicating that no default value is being used. Previously, I believe the default values for CoDel limiters were 5, 100, 1500, 10240, and 1024 respectively.

I am seeing this issue on multiple devices running 24.03 and 24.11. Something might have changed starting with 23.09/23.09.1, as I recall finding several firewalls with existing limiters that showed 0 for interval after being upgraded to 23.09/23.09.1.


Files

clipboard-202502081755-fsxmb.png (99.5 KB) clipboard-202502081755-fsxmb.png Jordan G, 02/08/2025 11:55 PM
Actions #1

Updated by Jordan G 2 months ago

following the documentation and creating a new limiter using taildrop/fqcodel leaving all values blank except the initial bandwidth entry produces the defaults after saving for me on 24.11

Actions #2

Updated by Andrew Almond about 2 months ago

I tested again on the device that I was creating the blank limiters, and now it is creating them correctly with default values.
I have run into this several times on different devices, but now the behavior appears to be intermittent.
I will try to perform more testing and see if I can find a pattern or specific way to cause a FQ_CODEL limiter to be created with no default values.

Actions #3

Updated by Jordan G about 2 months ago

thanks for confirming that it seems to be working for you now and please feel free to update if you are able to isolate the conditions or steps necessary to recreate the issue. setting to incomplete for the time being.

Actions #4

Updated by Jordan G about 2 months ago

  • Status changed from New to Incomplete
Actions

Also available in: Atom PDF