Batman log spam from

Hi :slight_smile:

There is an extra VLAN on my network to keep some home appliances in check.
For two of the routers, the batman mesh carries this VLAN (so that multicast traffic from appliances doesn't spread too far). The others don't have the VLAN.

Sadly, the routers without the VLAN complain every ~10 seconds when they receive the batman beacon:

Sun Aug 13 21:05:44 2023 kern.info kernel: [23244.471710] batman_adv: bat0: adding TT local entry 11:22:33:44:55:66 to non-existent VLAN 7
Sun Aug 13 21:05:55 2023 kern.info kernel: [23254.709286] batman_adv: bat0: adding TT local entry 11:22:33:44:55:66 to non-existent VLAN 7
Sun Aug 13 21:06:05 2023 kern.info kernel: [23264.951507] batman_adv: bat0: adding TT local entry 11:22:33:44:55:66 to non-existent VLAN 7
Sun Aug 13 21:06:15 2023 kern.info kernel: [23275.188781] batman_adv: bat0: adding TT local entry 11:22:33:44:55:66 to non-existent VLAN 7

In general, I like this setup because I can just swap the ethernet cable when we house non-family guests so they don't go directly into the LAN (and access my printer and such).

I've already given both groups of routers different passwords so they don't connect to each other but the message appears is also triggered by the beacon on the cable network.
Is it possible to ignore those unknown broadcasts or make the batman networks distinct from each other?
Or is there a way to bridge only the untagged part of the ethernet interface (like lan.untagged)?

See solution here:
https://www.open-mesh.org/doc/batman-adv/Faq.html#vlan-forwarding-doesn-t-work
Only the ip link add link bat0 name bat0.7 type vlan id 7 version worked for me, not the bridge vlan one.