Back to matrix

F23-BA: Yes

Rationale

An attached Ethernet client can move between mesh attachment nodes while retaining its MAC/VLAN identity. Local learning detects the move, sends a roaming advertisement to the former originator, and updates translation-table ownership; the receive path updates the global client entry and forwarding handles the old local entry marked roaming. This preserves the L2 endpoint and frame service without requiring an application peer relationship restart. The witness is attached-client roaming within one mesh/VLAN, not arbitrary inter-network mobility or migration of the mesh originator itself. MAC identity is not cryptographic authentication. Loss, convergence delay, client isolation and upper-layer timeouts still limit continuity.

Assessment method

Linux 6.12 translation-table and forwarding source analysis; no execution

Source context

Linux 6.12 batman-adv client roaming and translation table

Outstanding qualification

With Linux 6.12, move a native Ethernet client retaining MAC/VLAN between two mesh attachment nodes during bidirectional traffic. Verify roaming advertisements, translation-table ownership and continued frame delivery, including traffic through the old node. Pin IV/V for execution, measure delay/loss and test rapid moves and isolation settings. No live mesh test performed.

Public sources