netdev - Re: inter-qdisc communication?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49bb3aa4-a6d0-7f38-19eb-37f270443e7e@tarent.de>
Date:   Sat, 27 Aug 2022 02:45:02 +0200 (CEST)
From:   Thorsten Glaser <t.glaser@...ent.de>
To:     Jakub Kicinski <kuba@...nel.org>
cc:     netdev@...r.kernel.org
Subject: Re: inter-qdisc communication?

On Fri, 26 Aug 2022, Jakub Kicinski wrote:

> How do you add latency on ingress? 🤔 
> The ingress qdisc is just a stub to hook classifiers/actions. 

Oh, damn. Then, I guess, I’ll have to do that on egress on
the other interface, which makes it at least symmetric for
passing traffic but catch not the set of traffic it should.
Especially not the traffic terminating locally. Meh.

The question remains the same, just the use case magically
mutated under me.

(Maybe if there were documentation like an intro to qdisc
writing like I asked for already, I’d have known that.)

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
╱ ╲ header encryption!
                        ****************************************************