Hi, <br><br>I have a couple of questions regarding BATMAN and BATMAN-ADV<br><br>I do not understand what the transmission quality in OGMs is for. From my reading of the RFC draft, route selection is done based on the number of OGMs received for a specific destination within a sliding window of sequence numbers. I did catch a comment in the source code about  transmission quality it being used for bidirectional link detection, but there I couldn&#39;t find a mention of transmission quality in the draft RFC.<br>
<br>I have been looking at BATMAN and BATMAN-ADV OGMs in Wireshark. It seems that the BATMAN L3 OGMs have 18 bytes of BATMAN information on top of the 802.11 header (24bytes) LLC (8 bytes) IP header (20 bytes). Comparatively, the BATMAN-ADV OGMs comprise of a 802.11 header (24bytes) LLC (8 bytes) and 26 Bytes of BATMAN data. Now because Wireshark does not recognise BATMAN-ADV frames. I don&#39;t know what is being used for the extra 8 bytes of batman data. I guess the originator and receiver portions of the packet are now 6 byte MAC addresses rather than 4 byte IP addresses. However, this does not account for extra 8 bytes used for BATMAN-ADV.<br>
<br>In the future, it seems like BATMAN-ADV will get the majority of the developer attention. Other than not having to asign IP addresses, which does seem pretty cool, I am finding it hard to see &#39;major&#39; advantages of one versus another. This advantage also seems to be slightly offset because it now becomes harder to get gateway information. Is this right? <br>
<br>Does working at the data link layer make it easier to extract, neighbour SNR&#39;s or bit rates from the wireless driver? What about power control? I&#39;m just throwing ideas around here (I haven&#39;t thought this through) but could you have a power save mode whereby if the device is battery powered and has &gt; 8 neighbours, then slowly reduce the transmission power until neighbours is &lt; 4 or mains powered batman neighbours is &lt;2.<br>
<br>Thank you very much for your time<br>Dave<br>