Closed raenye closed 7 months ago
Thanks for the ticket. Also saw this after updating some of our office APs to 23.05.
There is nothing to be done by the proto. So I will simply add a stub function.
Thanks for the quick fix.
BTW, now that I read the code, does it even make sense to use batadv_vlan
for VLANs without AP isolation? does it serve to solve problems such as https://forum.openwrt.org/t/batman-log-spam-from/168516?
Thanks for the quick fix. BTW, now that I read the code, does it even make sense to use
batadv_vlan
for VLANs without AP isolation? does it serve to solve problems such as https://forum.openwrt.org/t/batman-log-spam-from/168516?
Yes and no.
It doesn't have any direct affect by toggling the ap_isolate setting. But netifd should automatically create the VLAN in this case - just because you reference a VLAN as ifname
. And if something created the VLAN then batman-adv will no longer complain about "non-existent VLAN"
But adding bat.X
to a bridge would serve the same purpose wrt netifd
, won't it?
Maintainer: @simonwunderlich Environment: multiple (mediatek/fiilogic, mediatek/mt7622, ramips/mt7621, ath79/generic
Description: There is no implementation of
proto_batadv_hardif_teardown
infiles/lib/netifd/proto/batadv_vlan.sh
, which causes the following error in the log:Not sure if something really needs to be done, or it's just log litter. Thanks!
Relevant part of
/etc/config/network
: