| 18 Feb 2026 |
|  antifuchs joined the room. | 02:00:38 |
| 19 Feb 2026 |
|  ginkogruen joined the room. | 01:30:04 |
|  Lan Tian changed their profile picture. | 08:00:27 |
|  Wilkuu [SNT] {main: @wilkuu:wilkuu.xyz} changed their display name from wilkuu to Wilkuu [SNT] {main: @wilkuu:wilkuu.xyz}. | 21:08:12 |
| 20 Feb 2026 |
 Sandro 🐧 | General KDE Connect breaks :) | 02:36:21 |
| Sandro 🐧 | whose support need some training that NAT64 is not IPv4 NAT :) | 02:36:59 |
| 21 Feb 2026 |
|  h7x4 changed their profile picture. | 19:25:18 |
| h7x4 changed their profile picture. | 19:30:11 |
| h7x4 changed their profile picture. | 19:33:35 |
| 22 Feb 2026 |
| antifuchs | hah, so I have just learned that nixos-nftables-firewall is pretty suboptimal in terms of performance | 01:49:39 |
| antifuchs | a machine that handles 10Gb/s of traffic easily will struggle with this zone config that I applied to it just now (about 170 handles) | 01:51:06 |
|  Haze joined the room. | 02:54:08 |
| antifuchs | (Update, no, that’s not it, the NIC just didn’t have GRO turned on) | 05:07:04 |
|  problems changed their profile picture. | 22:11:02 |
|  mei 🌒& changed their profile picture. | 22:53:36 |
| antifuchs | so, somewhat serious question though, I don't think boot.kernel.sysfs.class.net.eno8np0.device.sriov_numvfs = 32; is working; the path never triggers, even though the file exists. when I manually start the service, it applies the setting; is that boot.kernel.sysfs handling broken somehow, or am I expecting it to do something impossible? | 23:35:29 |
| 23 Feb 2026 |
| Sandro 🐧 | I had before that I needed to manually load a kernel module early on (as in with the option for it) to make the sysfs paths available when the sysfs service starts | 13:02:08 |
| antifuchs | huh, do you remember what kernel module that is? | 16:29:16 |
