- Node 1 could reach Node 2 directly over the IBSS subnet.
- Node 3 could reach Node 2 directly over the IBSS subnet.
- Direct IBSS/IP reachability between Node 1 and Node 3 was not observed.
- BATMAN-adv neighbor tables matched the expected three-node topology.
- BATMAN-adv originator tables selected Node 2 as the next hop between the two edge nodes.
- After mesh convergence, Node 1 and Node 3 communicated successfully through their
bat0addresses.
1. Test Topology
The test used the following addresses:
The two subnets have different purposes:
The decisive test topology was:
2. IBSS State
The captured terminal output confirms that the boards joined the same IBSS cell. Condensed captured output:wlan0 operating in IBSS mode on channel 1 at 2412 MHz.
3. Direct IBSS Evidence
The first test establishes which nodes were directly reachable using thewlan0 IBSS addresses.
Node 1
Node 1 could reach Node 2:Node 3
The reverse side was also tested. Node 3 could reach Node 2:A failed ping here shows that direct IBSS/IP reachability was not observed. By itself, it should not be interpreted as absolute proof that no physical radio link exists; it is evaluated together with the following BATMAN-adv neighbor and originator tables.
4. BATMAN-adv Neighbors
After the direct topology was established, BATMAN-adv was enabled on all three boards.Node 1
The captured neighbor table contained only Node 2:Node 2
The captured neighbor table contained both edge nodes:Node 3
The captured neighbor table contained Node 2:
The BATMAN-adv neighbor tables therefore match:
5. Forwarding Path
A successful endpoint ping alone is not sufficient to identify the forwarding path. For this reason, the BATMAN-adv originator table was also inspected.Node 1 to Node 3
Condensed relevant entries captured on Node 1:Node 3 to Node 1
Condensed relevant entries captured on Node 3:
The originator tables provide direct routing evidence that the remote edge node is reached through Node 2.
6. End-to-End Mesh Evidence
The final test uses thebat0 addresses rather than the direct IBSS addresses.
A short convergence interval was observed after BATMAN-adv startup. Initial bat0 ping attempts could fail while neighbor and originator information was still being learned. After the tables stabilized, the final captured tests succeeded in both directions.
Node 1 to Node 3
An initial attempt before convergence produced:Node 3 to Node 1
An initial attempt before convergence produced:bat0 tests:
7. Result
The captured evidence can be summarized as follows:
The verified forwarding path is:
The failed direct edge-to-edge IBSS pings, successful direct communication with Node 2 from both sides, BATMAN-adv neighbor tables, originator/next-hop information, and successful bidirectional
bat0 pings together demonstrate multi-hop Layer 2 forwarding through Node 2 in the tested topology.