Please check crash report for Limiters
-
@stephenw10 No, after this crash I removed Limiters and going over traffic shaping wizard. Did set OpenVPN clients as separate interfaces WAN and got this altq bug now.
-
@stephenw10 No, after this crash I removed Limiters and going over traffic shaping wizard. Did set OpenVPN clients as separate interfaces WAN and got this altq bug now.
@stephenw10 said in Please check crash report for Limiters:
What the exact steps required to replicate this Limiters issue?
I told, with Limiters active (Floating rule as well active on WAN) I removed 2 queues from settings. Before get set 3queues on each Limiters and during removing 2 of them was crashed!
-
Were you routing traffic through those queues or through the parent limiter? I can't replicate that here.
-
@stephenw10 said in Please check crash report for Limiters:
through those queues
-
@stephenw10 said in Please check crash report for Limiters:
through the parent limiter
Sorry misclick
-
So rules were set to use the parent limiter not any of the queues you removed directly?
-
@stephenw10 If you mean floating rule, I did ll the same as described in pfsense docs with a setting against bufferbloat, only add more 2 queues during set up on the same parent Limiters and removed later 2 of them and remain one queue only
-
Ah, OK so now we're getting somewhere. You had the Limiters setup for codelq.
-
@stephenw10 Yes, during set up
Queue Management Algorithm
: CodelScheduler
: FQ CodelECN checked on parent and queues as well
-
Ok, let me see if I can replicate that.
