F09-BA: Yes
Rationale
With native bonding enabled, batadv_find_router rotates eligible first-hop candidates across outgoing interfaces, retaining the last candidate rather than hashing an application flow to one route. A stream of frames to one destination can therefore use A-B-D and A-C-D concurrently. Select BATMAN_IV, two comparable eligible routes and active interfaces. The common scheduler also has comparator support in BATMAN_V, but the executable witness is fixed to IV. This is optional first-hop packet distribution, not loss-triggered failover, duplication, guaranteed disjointness or a throughput claim. No new transport layer is added.
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
Set BATMAN_IV and bonding=1 on a two-interface source. Establish comparable routes to one destination via B and C. Capture consecutive frames from one communication on both initial branches; verify useful delivery and record reordering. Default bonding=0 is not the credited configuration.