Feature request was approved and "completed" pror to 9.0 release then they missed 9.0 I was told it was going to be in 9.1 but I don't see it in release notes
Question to those in the know (Sophos Devs): are the known issues (as last reported at the bottom of the CoDel wiki page here: codel - Wiki - Bufferbloat) accounted for / corrected? If not, is there a way to turn this on or off, or is it just compiled into the kernel?
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
As per my knowledge and experience codel algorithm can make into 9.1 but you have need much knowledge and experience to make it.
I'm not sure what you were trying to say exactly but if your implying the CoDel algorythm is hard to configure that should be wrong as far as I know it has no parameters other than on / off
I think he meant that integrating it into the kernal would be difficult. In fact, I think I read in another thread that the work had been started a while ago and that it was completed for 9.1.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
Question to those in the know (Sophos Devs): are the known issues (as last reported at the bottom of the CoDel wiki page here: codel - Wiki - Bufferbloat) accounted for / corrected? If not, is there a way to turn this on or off, or is it just compiled into the kernel?
Its off by default. If QOS is enabled for a particular interface,
the default kernel qdisc (pfifo_fast) is replaced with fq_codel qdisc.
If you have traffic classes enabled, the root qdisc is hfsc like in V8 and 9.0,
except that the leaf qdiscs (think "each bandwidth pool") has its own
fq_codel (v7.0 to v9.0 used sfq qdisc, 9.1 merely replaces sfq with fq_codel in this case). As for your question, we only use fq_codel (fair queueing variant) of codel.
If you find that some flows (e.g. interactive traffic) are badly impacted by bulk traffic, you can prevent it by moving one of those to its own pool, then they will
by treated separately (each has its own fq_codel, independently scheduled).
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
