Sven Eckelmann

> .. or to the actual driver you are referring to ... my good guess was its ath9k. Since the change mentions ath9k everywhere and is patching ath9k - yes,...

If you only see these lines when your click restart then it looks like you have a problem with your wireless interface. ~~Btw. your mesh_rssi_threshold looks bogus and should often...

> They can connect to each other when only using 802.11s mode. But if you don't see the messages that phy1-mesh0 is added to bat0 (and is activated), it looks...

@simonwunderlich according to https://github.com/openwrt/openwrt/issues/14904#issuecomment-2649606720 , this was fixed in OpenWrt 24.10. Maybe we want to close this one

According to https://github.com/openwrt/openwrt/issues/14904#issuecomment-2649606720 , this was fixed in 24.10

> But to better understand that, why would you regularly enter an overdue task in Nextcloud? I don't. I enter a task which will become due in the near future...

@ambassador86 your change 582d09615bdcd9d9b6cb5ee74173ab78af3d846d is missing some follow up changes to support the throughput metric (BATADV_ATTR_THROUGHPUT) in: * package/gluon-mesh-batman-adv/src/respondd.c * package/gluon-status-page-mesh-batman-adv/src/neighbours-batadv.c * package/gluon-radv-filterd/src/gluon-radv-filterd.c (ok, this came after your change) Right...

Basic steps (just take this as a rough idea - not the complete solution) which someone has to do are following: diff --git a/package/gluon-mesh-batman-adv/src/respondd.c b/package/gluon-mesh-batman-adv/src/respondd.c index 810dfc59..b810eb71 100644 --- a/package/gluon-mesh-batman-adv/src/respondd.c...

> quite cool to see 10/15 PRs already merged in 17 days since then. While one has just been superseeded and one was put on hold to work on redoing...

@hailfinger Actually, @sharadanand would have been the one who should have done this. But if I find time, I can also go through this and prepare a PR. Just don't...