G04-BA: Yes
Rationale
Originator advertisements and neighbor selection run at each mesh node; client translation originates at its attachment, and TT requests can be answered by the responsible originator or a peer with suitable state. Native intra-mesh traffic does not require one central directory, controller or gateway. Added nodes/links can distribute forwarding across independent branches and client attachment work across originators. This satisfies the absence of an obligatory fixed coordination point, not arbitrary horizontal scalability: replicated originator/TT state and broadcast overhead remain, and explain the separate G01/G03 No results.
Assessment method
Pinned primary-source inspection and bounded configuration/topology inference; no execution
Source context
Linux v6.12 source; NET/ROM 1.3 manual where indicated
Outstanding qualification
Operate independent communicating pairs on separate mesh branches with gateway mode off; remove an unrelated originator and verify surviving branches and distributed TT response roles. Measure replication/control costs separately; no linear scaling or global capacity claim.
Public sources
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/batman-adv/bat_iv_ogm.c
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/batman-adv/bat_v_ogm.c
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/batman-adv/translation-table.c
- https://raw.githubusercontent.com/torvalds/linux/v6.12/net/batman-adv/routing.c