On 24/04/2015 6:26 a.m., Nick Rogers wrote:
> On Wed, Apr 22, 2015 at 10:35 PM, Amos Jeffries
> wrote:
>
>> On 23/04/2015 9:14 a.m., Nick Rogers wrote:
>>> After upgrading from 3.4.x to 3.5.x, I've noticed a new error message
>> with
>>> my squid configuration. Apparently squid 3.5 no longer allo
On Wed, Apr 22, 2015 at 10:35 PM, Amos Jeffries
wrote:
> On 23/04/2015 9:14 a.m., Nick Rogers wrote:
> > After upgrading from 3.4.x to 3.5.x, I've noticed a new error message
> with
> > my squid configuration. Apparently squid 3.5 no longer allows setting the
> > two lower-most ECN bits of the To
On 23/04/2015 9:14 a.m., Nick Rogers wrote:
> After upgrading from 3.4.x to 3.5.x, I've noticed a new error message with
> my squid configuration. Apparently squid 3.5 no longer allows setting the
> two lower-most ECN bits of the ToS byte.
Allowing it and leaving it up to admin was causing too muc
After upgrading from 3.4.x to 3.5.x, I've noticed a new error message with
my squid configuration. Apparently squid 3.5 no longer allows setting the
two lower-most ECN bits of the ToS byte. I realize that this is to
encourage people to use the modernized definition of ToS being a 6 bit DSCP
field a
