"
In the past on a linux-based firewall I had a more complex setup that was shielding my job (videocalls) against all the kids in the house that create traffic/bursts.
In Opnsense I thought to mirrow this but I found that the Codel stuff could do more than just keeping a fast track for my work. So initially I just shaped the traffic to avoid bufferbloat and postponed the further ideas. It seems to work somehow, because I get an A rating in the "waveform buffbloat test" with the shaper and a B without.
I have a typical German asymmetric connection 500mbit down/ 50 mbit up.
There are things that make me suspicious about the shaper and as I cannot find a real documentation all ends with guessing.
a) I loss a significant part of my 500/50 with a switched on shaper. It differs but 430/42 are good days.
That feeds the idea that even a stupid throttle would reduce presure on router and deliver such stable ping times.
b) The kernel throws this over limit messages and I cannot get a context.
My setup is fairly simple:
2 Pipes
- 500mbit for down
method: FlowQueue-CoDel, (FQ-)CoDel ECN enabled, quantum 1600, limit 1600
-50 for upstream
method: FlowQueue-CoDel, (FQ-)CoDel ECN enabled, quantum 160, limit 160
3 Queues all (FQ-)CoDel ECN true
Down Prio 1
Up prio10
up prio 1
4 Rules
ACK, DNS i push through the prio Queue
all the rest stays in default queues
I followed a basic tutorial and there are things that confuse me but do not get explained, like why nobody enables CoDel active queue management. Seems to be not the obvious or the UI has a terrible naming convention.
If you could bring some light in this, I am happy
Marc
In Opnsense I thought to mirrow this but I found that the Codel stuff could do more than just keeping a fast track for my work. So initially I just shaped the traffic to avoid bufferbloat and postponed the further ideas. It seems to work somehow, because I get an A rating in the "waveform buffbloat test" with the shaper and a B without.
I have a typical German asymmetric connection 500mbit down/ 50 mbit up.
There are things that make me suspicious about the shaper and as I cannot find a real documentation all ends with guessing.
a) I loss a significant part of my 500/50 with a switched on shaper. It differs but 430/42 are good days.
That feeds the idea that even a stupid throttle would reduce presure on router and deliver such stable ping times.
b) The kernel throws this over limit messages and I cannot get a context.
My setup is fairly simple:
2 Pipes
- 500mbit for down
method: FlowQueue-CoDel, (FQ-)CoDel ECN enabled, quantum 1600, limit 1600
-50 for upstream
method: FlowQueue-CoDel, (FQ-)CoDel ECN enabled, quantum 160, limit 160
3 Queues all (FQ-)CoDel ECN true
Down Prio 1
Up prio10
up prio 1
4 Rules
ACK, DNS i push through the prio Queue
all the rest stays in default queues
I followed a basic tutorial and there are things that confuse me but do not get explained, like why nobody enables CoDel active queue management. Seems to be not the obvious or the UI has a terrible naming convention.
If you could bring some light in this, I am happy
Marc
