F25-BA: Yes

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

A supported Ethernet client can use the selected batman-adv native L2 service through an available access bridge. It retains its local MAC and known peer MAC; no endpoint IP, ARP or cryptographic session is added. Linux 6.12 soft-interface transmission learns the client source MAC before forwarding, and reception removes mesh encapsulation before delivering the native Ethernet frame. With the remote peer still available in the live mesh, two 256-byte native payload frames consume 2 x (256 + 14 + 4 + 8 + 12) = 588 endpoint byte-times. This meets the 65,536-byte F25 budget without keeping an endpoint session alive.

Assessment method

Constructive documentary endpoint byte bound

Source context

Pinned Linux 6.12 native Ethernet client and mesh-interface source

Outstanding qualification

Configured leaf-client witness, not a sleeping mesh-router bound. One untagged Ethernet access port bridges to bat0; mesh hard interfaces remain separate. The available infrastructure and active remote peer retain working reachability, while the returning client is relearned from its first frame. Use loop-free single-access bridges with bridge-loop-avoidance disabled, no STP/LLDP/IP services or unrelated traffic on the client link. Disablement is a disclosed configuration choice, not the kernel default. BATMAN_IV, native bonding and gateway-off choices remain; mesh OGM/translation-table traffic outside this endpoint interface is excluded by the approved F25 boundary. No claim of zero mesh overhead, peer cryptographic authorization, runtime measurement, energy or global capacity.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.

round318-budget.json
round318-sources.json