Shaper: Bug or my Bad?

[dMopp]

Hi,

I have created the following:

Pipes:
Download / 95Mbit / fq_codel / ecn
Upload / 35 Mbit / fq_codel / ecn

Queues:
Download:
High Prio / Download-Pipe / Weight 100 / ecn
Medium Prio / Download-Pipe / Weight 25 / ecn
Low Prio / Download-Pipe / Weight 1 / ecn

Upload:
High Prio / Upload-Pipe / Weight 100 / ecn
Medium Prio / Upload-Pipe / Weight 25 / ecn
Low Prio / Upload-Pipe / Weight 1 / ecn

Flows
IN-Traffic from WAN to IPTV / Medium-Download-Prio
IN-Traffic from WAN to LAN / Low-Download-Prio


I can see in the status page, that all packages matching the correct flow etc. So this part is working.

Now my Problem:
When iam starting to Download something, the IP-TV starts to stutter a lot.

When i create ANOTHER Pipe (! not qeueue) with 25 Mbit and assign the flow to that pipe, the problem is solved.

Shouldnt the weight solve my issue? Why IPTV stutters even when the weight is way higher then the BULK traffic. ? And why another PIPE is solving the issue ?

PS: I have a 100/40MBit VDSL Line


Second Question:
With normalization, i can add DSCP Tags to packages. Does the shaper comes AFTER that so i can create DSCP based flows? this would be kind of diffserv behavior... But of cause, for that the upper question and problem needs to be solved first.

[dMopp]

In another forum, i got the hint, that fq-codel does NOT support weighted queues.

So with opnsense i have to select between bufferbloat or QoS ? Or is there a way to archive Bufferbloat A together with weighted queues.

PS: with OpenWRT i was reaching A+ Grade, even with a simple FritzBox its better 

[mimugmail]

Screenshots please

[dMopp]

Huh? From what?

The only question left doesn’t require screenshots (and as long I have to choice between weighted queue and less bufferbloat, I’ll chose less bufferbloat)

[mimugmail]

You say with fq codel queues are unsupported but see the correct floss in queues, so its not a question of queue or bloat

[dinguz]

Maybe you don't understand one another quite right. What the OP means is that:
- when using FlowQueue-Codel scheduler
- and using multiple queues
- a weight factor can be set on each queue, but it is not being honored. All queues are treated as if they have the same weight.

[mimugmail]

Maybe you don't understand one another quite right. What the OP means is that:
- when using FlowQueue-Codel scheduler
- and using multiple queues
- a weight factor can be set on each queue, but it is not being honored. All queues are treated as if they have the same weight.

This is not what the op said ..

[mimugmail]

Huh? From what?

The only question left doesn’t require screenshots (and as long I have to choice between weighted queue and less bufferbloat, I’ll chose less bufferbloat)

If this is the truth, then you can use WFQ and tick CoDel in the queues

[Monviech (Cedrik)]

I'm using the fq_codel on OPNsense with VDSL 250 and my bufferbloat is A+ with it.
https://www.waveform.com/tools/bufferbloat?test-id=f38a2885-4404-449b-8012-1de9252ec557

Also I have put like 20mbit/s download speed into a seperate pipe so I can watch videos without stutter.
So my main pipe is like 200mbit/s and my video pipe 20mbit/s. (Kinda like what you did) - There are queues inside but the weight isn't supported as you said, it's just to cleanly seperate traffic for me (like the TCP ACKs)
And I also have a seperate upload pipe.

[dMopp]

But in this case, every MBit going into a separated Pipe is missing for the BULK stuff, right? So the sum of all pipes should Benthe sum of total speed.

PS With WFQ+Codel Bufferbloat gets worse and IPTV starts to stutter again

And yes, queues are there with FQ_Codel but weight is useless.

[Monviech (Cedrik)]

@dMopp
Yes exactly, thats why you only see 200Mbit/s at my bufferbloat test.
I have 250Mbit/s, 30Mbit/s get eaten by the distance to the DSLAM, and 20Mbit/s get distributed to my IPTV pipe. That means only 200MBit/s is left for all the other stuff.

For me that works out though. Maybe you can find a better solution though.

[dMopp]

Sacrifice 25% for IPTV is hard. With my 100MBit this is not worth for me