C01-BA: Yes
Rationale
The selected native Ethernet service can preserve a client MAC address when the client loses its attachment to one batman-adv node and attaches to another reachable node in the same mesh and VLAN. The translation table maps that client address to its serving originator. Learning the client at the new node triggers roaming notification and translation-table updates, allowing traffic for the unchanged destination MAC to follow the new serving node.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
batman-adv translation-table roaming and RPL DAO target/parent separation
Outstanding qualification
Documentary witness for Linux 6.12 BATMAN_IV: a client keeps its locally administered unicast MAC and VLAN, reconnects through an already configured local Ethernet attachment, and transmits a frame so the new serving node learns it. Relays and destination remain reachable; client isolation and other forwarding policies must permit delivery. Notification, table-version reconciliation and route convergence can require retries. This is client attachment recovery, not only repair of an intermediate mesh link. No IP address mobility, cryptographic MAC authentication, cross-mesh roaming, seamless-session guarantee or automatic port authorization is inferred. The old attachment may fail without destroying the whole mesh; arbitrary partitions or simultaneous node failures are not guaranteed recoverable. No runtime experiment.
Public sources
- 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/send.c
- https://downloads.open-mesh.org/batman/papers/batman-adv_v_intro.pdf
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round532.html
- round532-sources.json