From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D8D2A3BA8E for ; Wed, 30 May 2018 16:44:12 -0400 (EDT) Received: by mail-lf0-x229.google.com with SMTP id d24-v6so6362904lfa.8 for ; Wed, 30 May 2018 13:44:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QdN61itSwslX2o5V975Sxt6RjBWzLbA4/2GiuAa81qs=; b=dwmxncLTAUUEZncI3S0A9fm6LEiBpHHHQ9wNJtSPPgl/t1VYnUAOCOrk7YCn/VdVBH VT+JpZ3okFqn8db8XluZTdZ9iL2GfGa+GVFH4honypFzB9hnvH7AI0B0+MLqNl3w62K1 2bFL18s0tmuuEhTG4mYz6fK5Qv8hWXOPOWr0eQMVFq8VEdhcy3h5fmxN90G0DuLnRXM8 1EtRARPam5UXOqTB4zggtdiwlQE2J+qojjoNvkf8LnhHb5Red7wmiyQbWe51w9hbqbWl LiU5bh6sEzS4p8slRVehOWBTo7QUt0ISBv0M4g7GYhrspCocHjTNaf77KVYu0JqVNZ4A zsNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QdN61itSwslX2o5V975Sxt6RjBWzLbA4/2GiuAa81qs=; b=JLWiN+exXXsg0hkuNB7DVF0wIBe0BlssNGGlBKhG/+OxjglxJBNTgoY+kMRiccZNrB /IqmQfFx6NffUIAN7Exa36I2bDdl052pEeDECAL35+AarkqZA3xsNztz/wdYx9S2rdi1 N4Pz8H34KdyI1RNZYsQ2MKhV7wms1VqyPORj7gIBIHOW7KjvRc5ZS0S/d+Dbz24vHKeH uKE5WVYZxUWhIhpngv6eiASv4lRkd5HjkbG9AwciKE4Fuixaq89g2qSiXdoLbUZTpihO ySI7wQY1bsqX59c0kpD+Gq6W8raTrjekAPYd9EApiueTxAf6M75lCC2K+sHl4JnxfjEP 3l+w== X-Gm-Message-State: ALKqPwfPu40/FuNBfNmlpYpNaM4jyUlrRyO1uWGyHVPhxXQv5o+A7dFp rrbR3yvqWpnX18tB87D382CUIUPTxncnIQ56rqg= X-Google-Smtp-Source: ADUXVKKkyaxz7D5i2z9iMUXivI8qGw0k9WIfhCims7mRBot212Zl/P39F2wPZKCMUgD+AUTqBp4wD2QOcPDm7w8z+kg= X-Received: by 2002:a19:6348:: with SMTP id x69-v6mr2679368lfb.104.1527713051603; Wed, 30 May 2018 13:44:11 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:9155:0:0:0:0:0 with HTTP; Wed, 30 May 2018 13:44:11 -0700 (PDT) In-Reply-To: References: <87muwyy34k.fsf@toke.dk> <87tvqoc3vl.fsf@toke.dk> <87r2lsc2dm.fsf@toke.dk> From: Georgios Amanakis Date: Wed, 30 May 2018 16:44:11 -0400 Message-ID: To: Dave Taht Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , Cake List Content-Type: text/plain; charset="UTF-8" Subject: Re: [Cake] Fwd: Does the latest cake support "tc filter"? X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2018 20:44:13 -0000 I don't have an explicit use case right now, but it gives somewhat greater flexibility in classifying packets. Particularly in the ingress mode with ifb (this would mostly apply to an end-device, not so much to traffic being forwarded through a router). We cannot set DSCP flags on incoming packets, since they just arrived. However, we can use a filter on cake to assign them explicitly to a tin. We can do the following: #tc qdisc add dev enp1s0 ingress handle ffff #tc qdisc add dev ifb0 root handle 8002 cake bandwidth 11800kbit diffserv3 ingress #tc filter add dev ifb0 parent 8002: protocol ip \ u32 match ip src 1.2.3.4/32 \ action skbedit priority 8002:3 #tc filter add dev enp1s0 parent ffff: protocol all \ u32 match u32 0 0 \ action mirred egress redirect dev ifb0 George