On 21/12/15 15:36, Jonathan Morton wrote:
> In that context, the “squash” and “wash” features truly baffle me.  I’d prefer to see them both gone.  Either you want to *use* Diffserv, in which case downstream networks might also benefit from the same markings, or you want to *ignore* it, in which case you might as well leave the existing marks alone, or you want to do something more sophisticated that Cake’s core feature set doesn’t support.
>
> In short, Cake is *not* the right place to change the DSCP field.  A separate qdisc could be written to do that job with minimal overhead and a dedicated configuration interface, and be inserted either before or after Cake as required.  Or we could wait for pre-ingress-qdisc firewall rules to become available.
Feel free to remove.  If squash shouldn't be there, then neither should
wash.  It was an idea to split out the use of diffserv markings vs the
clearing of them that the original "squash" option implemented into
'diffserv/squash/wash".  Bad ideas shouldn't be included so get rid of
it :-)

Kevin