Project

General

Profile

Actions

Bug #7886

closed

PRIQ, priority of 0 cannot be saved in GUI, GUI attempts to save a 0 value but actually ends up storing it as the default of 1

Added by jake xanaro over 7 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/21/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

PRIQ, priority of 0 cannot be saved in GUI, GUI attempts to save a 0 value but actually ends up storing it as the default of 1

This effectively limits the levels of filtering you can use in PRIQ from 8 to 7.

Having 8 levels of filtering can be very useful when using PRIQ.
I read someplace that PRIQ will actually support 15 levels, however I am not sure if that is true, 15 would be great, but even just having 8 would be better.

also there is a typo, on PRIQ traffic shaping setup it references hfsc when you click into one of the children:

For hfsc, the range is 0 to 7. The default is 1. Hfsc queues with a higher priority are preferred in the case of overload.


Files

pfsense.JPG (87.3 KB) pfsense.JPG priq jake xanaro, 09/21/2017 12:34 PM
Actions #1

Updated by jake xanaro over 7 years ago

I also noticed that if you reorder and change the names of the priorities, and you have P2P catch-all set (default queue), after reordering and renaming your queues, so that they are nice and organized like in my screenshot. The system will actually keep sending P2P traffic to the old default queue (which you renamed to something else when reordering and changed the default queue to something else as well) as can be seen under status>queues while having traffic that should be getting caught by the P2P catchall(this one had me chasing my tail for a bit, couldnt figure out why traffic that should have gone to the P2P queue was going to my games queue LOL!)

My solution to fix this, after you reorder and rename your queues, do a backup of the traffic shaping section, then restore that backup.(this makes it honor your new queue priority and default queue settings)

One other thing I have noticed, sometimes you goto Status>Queues and queues that you know for sure should have close to nothing for PPS are up in the hundreds or even thousands, the workaround I have been using to get it to report correctly, goto your shaper: Firewall>Traffic Shaper, then click into any of your children to edit them such as q7_ACK and dont actually make any edits, just click the save button, and then hit apply. Now if you goto Status>Queues it will be reporting correctly.

Actions #2

Updated by jake xanaro about 6 years ago

I noticed that the GUI is now allowing me to save values higher than 7 for PRIQ! I also see that you can now save a value as 0, Excellent!

I am not sure when this finally got fixed, but this ticket can now be closed, I would close it myself but I do not seem to have a way of doing that.

Actions #3

Updated by Jim Pingle about 6 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF