danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
hanetzer1 has joined #openwrt-devel
hanetzer has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
Strykar has quit [Quit: /quit]
Nilsro_ has joined #openwrt-devel
Strykar has joined #openwrt-devel
Nilsro has quit [Ping timeout: 480 seconds]
hanetzer has joined #openwrt-devel
hanetzer1 has quit [Ping timeout: 480 seconds]
Stat_headcrabbed has joined #openwrt-devel
rua has quit [Quit: Leaving.]
valku has quit [Quit: valku]
sorinello has joined #openwrt-devel
rua has joined #openwrt-devel
killgufo has quit [Ping timeout: 480 seconds]
killgufo has joined #openwrt-devel
ptudor has quit [Read error: Connection reset by peer]
ptudor has joined #openwrt-devel
Borromini has joined #openwrt-devel
mrkiko has joined #openwrt-devel
n3ph has joined #openwrt-devel
Borromini has quit [Quit: Lost terminal]
<f00b4r0>
nbd: probably silly question: is it expected that running 'tc filter dev <DEV> ingress protocol all prio 512' on a DEV that has an eBPF program attached (the one mentioned earlier) results in the ingress program being unloaded, even though 'tc filter show dev <DEV>' didn't show any active filter on the interface?
<f00b4r0>
(trying to solve a clash between eBPF and bandwidth throttling)
<f00b4r0>
s/unloaded/detached/
ptudor has quit [Read error: Connection reset by peer]
<f00b4r0>
oh, tc filter show dev <DEV> ingress
<f00b4r0>
i see. conflict of priority
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
<f00b4r0>
hauke: please make sure that mt76 gets updated then. It seems to finally fix a long standing issue with mt7915e radios
hanetzer has quit [Ping timeout: 480 seconds]
<f00b4r0>
(would also be nice if #11650 could eventually be fixed because it's a real PITA, but sadly it doesn't look like it's going to happen)
rua has joined #openwrt-devel
<hauke[m]>
f00b4r0: do you have a link to the commit fixing it?
<f00b4r0>
hauke[m]: fixing what?
<enyc>
hauke: Are you aware of the slab-leak parlaver (kernel side ram leaks related to hostapd and so-on)? I'm not sure has been properly bugreported that f00b4r0 nbd apparently know about?
<enyc>
apparently client traffic related to an extent; apparently 24.10.0 and 24.10.1 affected, have a script checking for excess SUnreclaim and running wifi up when needed to keep it in check .........
<enyc>
tried many wpad variants which does not seem to hep
merbanan has quit [Remote host closed the connection]
merbanan has joined #openwrt-devel
<enyc>
hauke: Alas not that I know about. It may be best I can do is re-test to see if 24.10.2 fixes-or-not. Some kernel patch/delta may be causing it, who knows!