netdev - tc-stab(8) dead link and question

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 PHC
Open Source and information security mailing list archives

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

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

Date:   Mon, 29 Aug 2022 17:33:12 +0200 (CEST)
From:   Thorsten Glaser <t.glaser@...ent.de>
To:     netdev@...r.kernel.org
Subject: tc-stab(8) dead link and question

Hi again,

from reading around in more documentation, I found “stab” mentioned
and that it refers to tc-stab(8).

First, the [1] link is dead; the Wayback Machine has as last version:
http://web.archive.org/web/20150606220856/http://ace-host.stuart.id.au/russell/files/tc/tc-atm/

Second… this might be something I’d need to take into account when
doing bandwidth limiting. How do I use the adjusted sizes?

Currently, I’m shaping by taking skb->len and multiplying with the
amount of ns per byte that can be calculated from the configured rate.
This (on ethernet, which I’m testing on; in prod it is possibly used
on WLAN instead but not always) already takes the Ethernet header into
account, but not the trailer apparently, but it would obviously need
per-packet overhead for DSL links, so I’m wondering which variables
I need to query, and how, for this.

Thanks,
//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!
                        ****************************************************