Dixi quod… >/usr/sbin/sshd -ddddde -o IPQoS='lowdelay throughput' >also works (isn’t that the pre-1:10.0p1-7+deb13u3 setting?).
ssh’ing out also fails unless -o IPQoS='lowdelay throughput' so it also affects the client. I then ran a test which TC octets pass through, by cloning https://github.com/mirabilos/ECN-Bits (an earlier project), 'cd c && make', then: $ ./server/server 11111 and: $ i=-1; while (( ++i < 256 )); do ./client/client 192.168.1.5 11111 $i; done The result is that the Fritzboxen do not generally drop packets with any TC octet (my first 0x49 didn’t pass, but it’s UDP, and on retry, it worked). However, if I start the server as… $ ./server/server +0xB8 11111 (meaning it will (try to) respond to each incoming packet with TC 0xB8‥0xBB), then no replies are registred at the client. I’m not sure whether this is something done by Linux itself or a device after it. Reversing the construct from above, i.e. the trixie system sending… 0x00‥0x9F, 0xC0‥0xFF pass, i.e. 0xA0‥0xBF are dropped, which is bit pattern 001xxx.xx (ToS.ECN), which corresponds to precedence 1 in the old model, or in DSCP, decimal 8‥15, which Wikipedia’s list shows as CS1, ?, AF11, ?, AF12, ?, AF13, ?. Unfortunately, I’m unable to get either of the laptops to switch APs (sudo iwconfig wlan0 ap …), but I did get an iwlwifi crash on attempting that… so I cannot test changing Fritzboxen atm. Gruß //Thorsten -- Thorsten Glaser Linux / Unix Developer Tel.: +49 160 91168501 E-Mail: [email protected] B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de/ GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537

